From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
Leif Lindholm <leif.lindholm@linaro.org>,
Laszlo Ersek <lersek@redhat.com>,
"Carsey, Jaben" <jaben.carsey@intel.com>,
Ruiyu Ni <ruiyu.ni@intel.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>,
Kelly Steele <kelly.steele@intel.com>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Subject: Re: [PATCH 0/4] Shell/Quark/ArmPkg: promote shell app FILE_GUID to proper GUID
Date: Wed, 22 Mar 2017 15:38:27 +0000 [thread overview]
Message-ID: <CAKv+Gu8qSQ7GZcTp9c8bAFnq+NTex+_E0uvw6u1gO80yaQfRBQ@mail.gmail.com> (raw)
In-Reply-To: <1490191448-22398-1-git-send-email-ard.biesheuvel@linaro.org>
On 22 March 2017 at 14:04, Ard Biesheuvel <ard.biesheuvel@linaro.org> wrote:
> To avoid the need for open coded GUID declarations that copy the FILE_GUID
> of the Shell app, add it to ShellPkg.dec and replace existing references.
>
Thanks all
I went ahead and pushed
2edc20c46863 ShellPkg: add GUID declaration for FILE_GUID of UEFI
Shell app to package
07548e17c5ff ArmPkg/PlatformBootManagerLib: refer to Shell FILE_GUID directly
c81c2c0fc453 ArmVirtPkg/ArmVirtQemu: refer to Shell app via its declared GUID
because I have some stuff queued up that depends on it.
> Ard Biesheuvel (4):
> ShellPkg: add GUID declaration for FILE_GUID of UEFI Shell app to
> package
> QuarkPlatformPkg/PlatformBootManagerLib: use new UefiShellFileGuid
> definition
> ArmPkg/PlatformBootManagerLib: refer to Shell FILE_GUID directly
> ArmVirtPkg/ArmVirtQemu: refer to Shell app via its declared GUID
>
> ArmPkg/Library/PlatformBootManagerLib/PlatformBm.c | 5 ++---
> ArmPkg/Library/PlatformBootManagerLib/PlatformBootManagerLib.inf | 3 ++-
> ArmVirtPkg/ArmVirtQemu.dsc | 1 -
> ArmVirtPkg/ArmVirtQemuKernel.dsc | 1 -
> ArmVirtPkg/Library/PlatformBootManagerLib/PlatformBm.c | 2 +-
> ArmVirtPkg/Library/PlatformBootManagerLib/PlatformBootManagerLib.inf | 6 +++---
> QuarkPlatformPkg/Library/PlatformBootManagerLib/PlatformBootManager.c | 4 +---
> QuarkPlatformPkg/Library/PlatformBootManagerLib/PlatformBootManagerLib.inf | 2 ++
> ShellPkg/ShellPkg.dec | 3 +++
> 9 files changed, 14 insertions(+), 13 deletions(-)
>
> --
> 2.7.4
>
next prev parent reply other threads:[~2017-03-22 15:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 14:04 [PATCH 0/4] Shell/Quark/ArmPkg: promote shell app FILE_GUID to proper GUID Ard Biesheuvel
2017-03-22 14:04 ` [PATCH 1/4] ShellPkg: add GUID declaration for FILE_GUID of UEFI Shell app to package Ard Biesheuvel
2017-03-22 15:13 ` Carsey, Jaben
2017-03-22 15:19 ` Ard Biesheuvel
2017-03-22 15:21 ` Carsey, Jaben
2017-03-22 15:39 ` Kinney, Michael D
2017-03-22 15:41 ` Carsey, Jaben
2017-03-22 15:54 ` Andrew Fish
2017-03-22 14:04 ` [PATCH 2/4] QuarkPlatformPkg/PlatformBootManagerLib: use new UefiShellFileGuid definition Ard Biesheuvel
2017-03-22 15:43 ` Kinney, Michael D
2017-03-22 14:04 ` [PATCH 3/4] ArmPkg/PlatformBootManagerLib: refer to Shell FILE_GUID directly Ard Biesheuvel
2017-03-22 14:04 ` [PATCH 4/4] ArmVirtPkg/ArmVirtQemu: refer to Shell app via its declared GUID Ard Biesheuvel
2017-03-22 14:39 ` Laszlo Ersek
2017-03-22 15:38 ` Ard Biesheuvel [this message]
2017-03-22 15:39 ` [PATCH 0/4] Shell/Quark/ArmPkg: promote shell app FILE_GUID to proper GUID Carsey, Jaben
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=CAKv+Gu8qSQ7GZcTp9c8bAFnq+NTex+_E0uvw6u1gO80yaQfRBQ@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