All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Lawnick <ml.lawnick@gmx.de>
To: AKASHI Takahiro <takahiro.akashi@linaro.org>, u-boot@lists.denx.de
Subject: Re: RFC: exclude partitions from efi_selftest
Date: Thu, 16 Sep 2021 13:19:06 +0200	[thread overview]
Message-ID: <f11126eb-70d9-05d0-c1a7-dd718f9e95da@gmx.de> (raw)
In-Reply-To: <20210916093710.GA79717@laputa>

Am 16.09.2021 um 11:37 schrieb AKASHI Takahiro:
> 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:
>>>> - 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?
>

Hmm, I think the question is really clear, I don't know how to ask
differently. But as the original issue is cleared and this is only for
background understanding, let's drop it.

THX again to you and Heinrich for fast help.

--
KR
Michael

  reply	other threads:[~2021-09-16 11:19 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
2021-09-16 11:19                           ` Michael Lawnick [this message]
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=f11126eb-70d9-05d0-c1a7-dd718f9e95da@gmx.de \
    --to=ml.lawnick@gmx.de \
    --cc=takahiro.akashi@linaro.org \
    --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 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.