All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Lawnick <ml.lawnick@gmx.de>
To: u-boot@lists.denx.de
Subject: Re: RFC: exclude partitions from efi_selftest
Date: Thu, 16 Sep 2021 09:48:07 +0200	[thread overview]
Message-ID: <97df9fca-9d6c-1364-cfd8-ee9c417db96e@gmx.de> (raw)
In-Reply-To: <20db317b-a368-3dc0-8233-c702264e9ccf@gmx.de>

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?
- What is the reason/use to iterate through the recognized partitions
even twice (in .setup and .execute) if they aren't needed/used?

--
KR
Michael

  reply	other threads:[~2021-09-16  7:48 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 [this message]
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
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=97df9fca-9d6c-1364-cfd8-ee9c417db96e@gmx.de \
    --to=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 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.