From: "Ard Biesheuvel" <ardb@kernel.org>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: Sami Mujawar <sami.mujawar@arm.com>,
devel@edk2.groups.io, ardb+tianocore@kernel.org,
thomas.abraham@arm.com, Pierre.Gondois@arm.com,
Matteo.Carlini@arm.com, Akanksha.Jain2@arm.com,
Ben.Adderson@arm.com
Subject: Re: [PATCH edk2-platforms v1 1/1] Platform/ARM: Fix BootMonFS device path
Date: Fri, 3 Feb 2023 13:26:51 +0100 [thread overview]
Message-ID: <CAMj1kXFyc7TMDWEoVVaf-1=NgU0SwWp6L5Pzst0EgsBRwJDLHA@mail.gmail.com> (raw)
In-Reply-To: <20230202112844.bc7bde7minssk7ug@bogus>
On Thu, 2 Feb 2023 at 12:28, Sudeep Holla <sudeep.holla@arm.com> wrote:
>
> On Thu, Feb 02, 2023 at 11:21:38AM +0000, Sami Mujawar wrote:
> > The NOR Flash driver was recently moved from the Tianocore\edk2 repository
> > to the Tianocore\edk2-platforms repository at the following location:
> > Platform\ARM\Drivers\NorFlashDxe\NorFlashDxe.inf
> >
> > As part of this move the FILE_GUID for the NorFlashDxe.inf at the new
> > location was also updated from: 93E34C7E-B50E-11DF-9223-2443DFD72085
> > to: DE6AE758-D662-4E17-A97C-4C5964DA4C41
> >
> > Correspondingly, the device paths for the BootMonFs also requires to be
> > updated in gArmBootMonFsTokenSpaceGuid.PcdBootMonFsSupportedDevicePaths
> > so that the file system is correctly mounted.
> >
> > Therefore, update the BootMonFS device path for the platforms that
> > utilise it.
> >
> > Reported-by: Sudeep Holla <Sudeep.Holla@arm.com>
>
> Tested-by: Sudeep Holla <Sudeep.Holla@arm.com>
>
Merged as c855d03384f84413c51ae082de2ecd19f9e8d844
Apologies for the breakage
--
Ard.
prev parent reply other threads:[~2023-02-03 12:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 11:21 [PATCH edk2-platforms v1 1/1] Platform/ARM: Fix BootMonFS device path Sami Mujawar
[not found] ` <20230202112844.bc7bde7minssk7ug@bogus>
2023-02-03 12:26 ` Ard Biesheuvel [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-list 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='CAMj1kXFyc7TMDWEoVVaf-1=NgU0SwWp6L5Pzst0EgsBRwJDLHA@mail.gmail.com' \
--to=devel@edk2.groups.io \
/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