From: "Zeng, Star" <star.zeng@intel.com>
To: "Kinney, Michael D" <michael.d.kinney@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Zeng, Star" <star.zeng@intel.com>
Subject: Re: [PATCH 0/2] Fix ESRT out of date
Date: Wed, 8 Aug 2018 01:05:24 +0000 [thread overview]
Message-ID: <0C09AFA07DD0434D9E2A0C6AEB0483103BBA6388@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <E92EE9817A31E24EB0585FDF735412F5B8AB95B7@ORSMSX113.amr.corp.intel.com>
Agree, thanks very much. :)
Star
-----Original Message-----
From: Kinney, Michael D
Sent: Wednesday, August 8, 2018 9:02 AM
To: Zeng, Star <star.zeng@intel.com>; edk2-devel@lists.01.org; Kinney, Michael D <michael.d.kinney@intel.com>
Subject: RE: [PATCH 0/2] Fix ESRT out of date
Series Reviewed-by: Michael D Kinney <michael.d.kinney@intel.com>
The commit message in patch 2 should say
"(reset is not required"
Mike
> -----Original Message-----
> From: Zeng, Star
> Sent: Monday, August 6, 2018 3:29 AM
> To: edk2-devel@lists.01.org
> Cc: Zeng, Star <star.zeng@intel.com>; Kinney, Michael D
> <michael.d.kinney@intel.com>
> Subject: [PATCH 0/2] Fix ESRT out of date
>
> Cc: Michael D Kinney <michael.d.kinney@intel.com>
>
> Star Zeng (2):
> FmpDevicePkg FmpDxe: Need repopulate after SetImage is called
> MdeModulePkg ErstFmpDxe: Create ESRT in ReadyToBoot event
>
> FmpDevicePkg/FmpDxe/FmpDxe.c | 21 +--
> MdeModulePkg/Universal/EsrtFmpDxe/EsrtFmp.c | 239
> ++++++++++++----------------
> 2 files changed, 109 insertions(+), 151 deletions(-)
>
> --
> 2.7.0.windows.1
prev parent reply other threads:[~2018-08-08 1:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-06 10:28 [PATCH 0/2] Fix ESRT out of date Star Zeng
2018-08-06 10:28 ` [PATCH 1/2] FmpDevicePkg FmpDxe: Need repopulate after SetImage is called Star Zeng
2018-08-06 10:29 ` [PATCH 2/2] MdeModulePkg ErstFmpDxe: Create ESRT in ReadyToBoot event Star Zeng
2018-08-08 1:01 ` [PATCH 0/2] Fix ESRT out of date Kinney, Michael D
2018-08-08 1:05 ` Zeng, Star [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=0C09AFA07DD0434D9E2A0C6AEB0483103BBA6388@shsmsx102.ccr.corp.intel.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