public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: AKASHI Takahiro <takahiro.akashi@linaro.org>
To: Michael Lawnick <ml.lawnick@gmx.de>
Cc: u-boot@lists.denx.de
Subject: Re: RFC: exclude partitions from efi_selftest
Date: Thu, 16 Sep 2021 18:37:10 +0900	[thread overview]
Message-ID: <20210916093710.GA79717@laputa> (raw)
In-Reply-To: <e3f6399d-aa70-a7e5-3944-28ecad865d75@gmx.de>

On Thu, Sep 16, 2021 at 11:14:01AM +0200, Michael Lawnick wrote:
> Am 16.09.2021 um 10:02 schrieb AKASHI Takahiro:
> > On Thu, Sep 16, 2021 at 09:48:07AM +0200, Michael Lawnick wrote:
> > > Am 16.09.2021 um 09:15 schrieb Michael Lawnick:
> > > > Am 16.09.2021 um 09:12 schrieb AKASHI Takahiro:
> > > > > Please, as Heinrich suggested, add CONFIG_FS_FAT, in your U-Boot configuration.
> > > > > 
> > > > Hmm, I didn't understand that as a suggestion, but as a question for his
> > > > understanding. Of course I'll give it a try.
> > > > 
> > > Sometimes live is such easy. This fixed my issue, THX.
> > > 
> > > For the after-math / my understanding:
> > > - Do I understand correctly that the problem was that 'efi_selftest
> > > block device' requires FAT support? So shouldn't there be a dependency
> > > in CONFIG?
> > 
> > Strictly speaking, CONFIG_EFI_LOADER requires FAT per UEFI specification,
> > and actually it has 'imply FAT'. I don't know why Heinrich uses 'imply'
> > instead of 'select'.
> > 
> > > - What is the reason/use to iterate through the recognized partitions
> > > even twice (in .setup and .execute) if they aren't needed/used?
> > 
> > What line of code do you exactly mean by 'in .setup' (and in .execute)?
> 
> My understanding:
> efi_selftests register their methods separated by setup/execute/teardown.
> The central test control is taking tests from list and executes the
> three methods, unaware of which exact test is executed:
> lib/efi_selftest/efi_selftest.c

That is exactly what efi_selftest.c does.

> lib/efi_selftest/efi_selftest_block_device.c

And this is a test instance for block device test.
So what's your question?

-Takahiro Akashi

  reply	other threads:[~2021-09-16  9:37 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-14 14:56 RFC: exclude partitions from efi_selftest Michael Lawnick
2021-09-14 15:57 ` Heinrich Schuchardt
2021-09-15  9:56   ` Michael Lawnick
2021-09-15 10:42     ` Heinrich Schuchardt
2021-09-15 10:54       ` Michael Lawnick
2021-09-15 11:22         ` Heinrich Schuchardt
2021-09-15 11:36           ` Michael Lawnick
2021-09-15 15:06             ` Michael Lawnick
2021-09-16  7:12               ` AKASHI Takahiro
2021-09-16  7:15                 ` Michael Lawnick
2021-09-16  7:48                   ` Michael Lawnick
2021-09-16  8:02                     ` AKASHI Takahiro
2021-09-16  9:14                       ` Michael Lawnick
2021-09-16  9:37                         ` AKASHI Takahiro [this message]
2021-09-16 11:19                           ` Michael Lawnick
2021-09-15 12:00       ` Mark Kettenis
2021-09-16  6:59         ` AKASHI Takahiro

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=20210916093710.GA79717@laputa \
    --to=takahiro.akashi@linaro.org \
    --cc=ml.lawnick@gmx.de \
    --cc=u-boot@lists.denx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox