On Mon, 13 Feb 2023 at 18:46, Heinrich Schuchardt wrote:
>
> On 2/13/23 10:42, Masahisa Kojima wrote:
> > Hi Heinrich,
> >
> > On Mon, 13 Feb 2023 at 16:44, Heinrich Schuchardt
> > wrote:
> >>
> >> On 2/13/23 06:50, Masahisa Kojima wrote:
> >>> On Fri, 10 Feb 2023 at 20:57, Heinrich Schuchardt
On 2/13/23 10:42, Masahisa Kojima wrote:
Hi Heinrich,
On Mon, 13 Feb 2023 at 16:44, Heinrich Schuchardt wrote:
On 2/13/23 06:50, Masahisa Kojima wrote:
On Fri, 10 Feb 2023 at 20:57, Heinrich Schuchardt wrote:
On 2/2/23 10:24, Masahisa Kojima wrote:
Current eficonfig_print_msg() does not
Hi Heinrich,
On Mon, 13 Feb 2023 at 16:44, Heinrich Schuchardt wrote:
>
> On 2/13/23 06:50, Masahisa Kojima wrote:
> > On Fri, 10 Feb 2023 at 20:57, Heinrich Schuchardt
> > wrote:
> >>
> >> On 2/2/23 10:24, Masahisa Kojima wrote:
> >>> Current eficonfig_print_msg() does not show the return
>
On 2/13/23 06:50, Masahisa Kojima wrote:
On Fri, 10 Feb 2023 at 20:57, Heinrich Schuchardt wrote:
On 2/2/23 10:24, Masahisa Kojima wrote:
Current eficonfig_print_msg() does not show the return
value of EFI Boot/Runtime Services when the service call fails.
With this commit, user can know
On Fri, 10 Feb 2023 at 20:57, Heinrich Schuchardt wrote:
>
> On 2/2/23 10:24, Masahisa Kojima wrote:
> > Current eficonfig_print_msg() does not show the return
> > value of EFI Boot/Runtime Services when the service call fails.
> > With this commit, user can know EFI_STATUS in the error message.
On 2/2/23 10:24, Masahisa Kojima wrote:
Current eficonfig_print_msg() does not show the return
value of EFI Boot/Runtime Services when the service call fails.
With this commit, user can know EFI_STATUS in the error message.
Why do we need function eficonfig_print_msg()?
I cannot see why the
Current eficonfig_print_msg() does not show the return
value of EFI Boot/Runtime Services when the service call fails.
With this commit, user can know EFI_STATUS in the error message.
Signed-off-by: Masahisa Kojima
---
cmd/eficonfig.c | 95 +--
7 matches
Mail list logo