All of lore.kernel.org
 help / color / mirror / Atom feed
From: AKASHI Takahiro <takahiro.akashi@linaro.org>
To: Heinrich Schuchardt <xypron.glpk@gmx.de>
Cc: u-boot@lists.denx.de, Alexander Graf <agraf@csgraf.de>,
	Sughosh Ganu <sughosh.ganu@linaro.org>
Subject: Re: [PATCH] test/py: efi_capsule: aligned with efidebug syntax changes
Date: Tue, 20 Jul 2021 11:42:16 +0900	[thread overview]
Message-ID: <20210720024216.GE77259@laputa> (raw)
In-Reply-To: <d66ecefb-a134-1021-034f-c09d436ab8fd@gmx.de>

On Thu, May 20, 2021 at 05:14:36AM +0200, Heinrich Schuchardt wrote:
> On 5/10/21 10:21 AM, AKASHI Takahiro wrote:
> 
> In the subject: %s/aligned/align/

I think that the passive usage is grammatically correct here,
but I can fix it if you like.

> > After the commit c70f44817d46 ("efi_loader: simplify 'printenv -e'"),
> > "-all" option is no longer necessary.
> > Just remove them in the test script.
> 
> 'env print -e -all Capsule0000' leads to an error CMD_RET_USAGE.
> 
> Capsule0000 does not necessarily exist. Shouldn't we print CapsuleLast
> and CapsuleMax and check their value instead?
> 
> Shouldn't we restrict the output to EFI_CAPSULE_REPORT_GUID to be sure
> that the GUID of these variables is correct?

No. The whole aim of executing "env print -e" (or whatever else command)
was to invoke efi_init_obj_list(), hence efi_launch_capsules().
We don't have to care whether it fails or not.

In fact, this test case still works correctly even with "--all".
So this patch is just a cleanup. I will repost it.

-Takahiro Akashi

> Best regards
> 
> Heinrich
> 
> > 
> > Fixes: c70f44817d46 ("efi_loader: simplify 'printenv -e'")
> > Signed-off-by: AKASHI Takahiro <takahiro.akashi@linaro.org>
> > ---
> >   test/py/tests/test_efi_capsule/test_capsule_firmware.py | 6 +++---
> >   1 file changed, 3 insertions(+), 3 deletions(-)
> > 
> > diff --git a/test/py/tests/test_efi_capsule/test_capsule_firmware.py b/test/py/tests/test_efi_capsule/test_capsule_firmware.py
> > index 4697ca6f1c5c..9eeaae27d626 100644
> > --- a/test/py/tests/test_efi_capsule/test_capsule_firmware.py
> > +++ b/test/py/tests/test_efi_capsule/test_capsule_firmware.py
> > @@ -85,7 +85,7 @@ class TestEfiCapsuleFirmwareFit(object):
> > 
> >                   # need to run uefi command to initiate capsule handling
> >                   output = u_boot_console.run_command(
> > -                    'env print -e -all Capsule0000')
> > +                    'env print -e Capsule0000')
> > 
> >               output = u_boot_console.run_command_list([
> >                   'host bind 0 %s' % disk_img,
> > @@ -160,7 +160,7 @@ class TestEfiCapsuleFirmwareFit(object):
> > 
> >                   # need to run uefi command to initiate capsule handling
> >                   output = u_boot_console.run_command(
> > -                    'env print -e -all Capsule0000')
> > +                    'env print -e Capsule0000')
> > 
> >               output = u_boot_console.run_command_list([
> >                   'host bind 0 %s' % disk_img,
> > @@ -227,7 +227,7 @@ class TestEfiCapsuleFirmwareFit(object):
> > 
> >                   # need to run uefi command to initiate capsule handling
> >                   output = u_boot_console.run_command(
> > -                    'env print -e -all Capsule0000')
> > +                    'env print -e Capsule0000')
> > 
> >               output = u_boot_console.run_command_list(['efidebug capsule esrt'])
> > 
> > 
> 

      reply	other threads:[~2021-07-20  2:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-10  8:21 [PATCH] test/py: efi_capsule: aligned with efidebug syntax changes AKASHI Takahiro
2021-05-20  3:14 ` Heinrich Schuchardt
2021-07-20  2:42   ` AKASHI Takahiro [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210720024216.GE77259@laputa \
    --to=takahiro.akashi@linaro.org \
    --cc=agraf@csgraf.de \
    --cc=sughosh.ganu@linaro.org \
    --cc=u-boot@lists.denx.de \
    --cc=xypron.glpk@gmx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.