From: "Laszlo Ersek" <lersek@redhat.com>
To: devel@edk2.groups.io, pete@akeo.ie
Cc: afish@apple.com, liming.gao@intel.com
Subject: Re: [edk2-devel] [PATCH v2 0/2] PlatformBootManagerLib: Don't update progress if Pcd is 0
Date: Wed, 16 Oct 2019 18:36:22 +0200 [thread overview]
Message-ID: <791f06f4-b5eb-b77d-bd0f-9fa02bd55fc3@redhat.com> (raw)
In-Reply-To: <716f1268-882a-ad5f-31dc-679e549f68fc@redhat.com>
On 10/14/19 20:36, Laszlo Ersek wrote:
> On 10/14/19 17:03, Pete Batard wrote:
>> Changes from previous version:
>> - Additional empty comment lines above and below, to keep with existing comment
>> style
>> - Similar logic is applied to ArmVirtPkg/PlatformBootManagerLib, since the same
>> issue may manifest itself here.
>>
>> Pete Batard (2):
>> OvmfPkg/PlatformBootManagerLib: Don't update progress if Pcd is 0
>> ArmVirtPkg/PlatformBootManagerLib: Don't update progress if Pcd is 0
>>
>> ArmVirtPkg/Library/PlatformBootManagerLib/PlatformBm.c | 14 +++++++++++---
>> OvmfPkg/Library/PlatformBootManagerLib/BdsPlatform.c | 15 ++++++++++++---
>> 2 files changed, 23 insertions(+), 6 deletions(-)
>>
>
> Thanks. I'll add the BZ reference to patch#2 too, and then push the
> series tomorrow (with feedback tags from Phil and others picked up, of
> course). Every set should spend 24h on the list, before being pushed.
Pushed as commit range cd70b1a71d30..23ab8df01a2c.
Thanks!
Laszlo
prev parent reply other threads:[~2019-10-16 16:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-14 15:03 [PATCH v2 0/2] PlatformBootManagerLib: Don't update progress if Pcd is 0 Pete Batard
2019-10-14 15:03 ` [PATCH v2 1/2] OvmfPkg/PlatformBootManagerLib: " Pete Batard
2019-10-14 15:33 ` [edk2-devel] " Philippe Mathieu-Daudé
2019-10-14 15:03 ` [PATCH v2 2/2] ArmVirtPkg/PlatformBootManagerLib: " Pete Batard
2019-10-14 15:34 ` [edk2-devel] " Philippe Mathieu-Daudé
2019-10-14 18:36 ` [edk2-devel] [PATCH v2 0/2] PlatformBootManagerLib: " Laszlo Ersek
2019-10-16 16:36 ` Laszlo Ersek [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=791f06f4-b5eb-b77d-bd0f-9fa02bd55fc3@redhat.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