public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Ard Biesheuvel" <ard.biesheuvel@linaro.org>
To: "Wu, Hao A" <hao.a.wu@intel.com>
Cc: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	"Wang, Jian J" <jian.j.wang@intel.com>,
	 "Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] [PATCH v2] MdeModulePkg/DxeCapsuleLibFmp: avoid ESRT accesses at runtime
Date: Tue, 23 Apr 2019 00:03:05 +0200	[thread overview]
Message-ID: <CAKv+Gu9uxXJMGMX0FG3Hx1Z-dukw2EtWYsJAh4iYcY5PLvj69A@mail.gmail.com> (raw)
In-Reply-To: <B80AF82E9BFB8E4FBD8C89DA810C6A093C8C0A54@SHSMSX104.ccr.corp.intel.com>

On Mon, 22 Apr 2019 at 09:14, Wu, Hao A <hao.a.wu@intel.com> wrote:
>
> > -----Original Message-----
> > From: devel@edk2.groups.io [mailto:devel@edk2.groups.io] On Behalf Of Ard
> > Biesheuvel
> > Sent: Saturday, April 20, 2019 6:35 PM
> > To: devel@edk2.groups.io
> > Cc: Wu, Hao A; Wang, Jian J; Kinney, Michael D; Ard Biesheuvel
> > Subject: [edk2-devel] [PATCH v2] MdeModulePkg/DxeCapsuleLibFmp: avoid
> > ESRT accesses at runtime
>
> Hello Ard,
>
> It seems to me v2 patch makes a copy of the ESRT for runtime usage (rather
> than avoid using ESRT), so the title of the commit may need update as
> well.
>
> Could you help to update the patch subject when you push the change?
>
> Other than that, the patch looks good to me. But I would like to see if
> Mike has additional comments on this:
>
> Acked-by: Hao Wu <hao.a.wu@intel.com>
>

Thanks Hao. I will modify the subject to 'clone ESRT for runtime access'

Mike: any comments?

  reply	other threads:[~2019-04-22 22:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-20 10:34 [PATCH v2] MdeModulePkg/DxeCapsuleLibFmp: avoid ESRT accesses at runtime Ard Biesheuvel
2019-04-22  7:14 ` [edk2-devel] " Wu, Hao A
2019-04-22 22:03   ` Ard Biesheuvel [this message]
2019-04-22 22:37     ` Michael D Kinney
2019-04-22 22:40       ` Ard Biesheuvel
2019-04-22 23:02         ` Michael D Kinney
2019-04-23 16:52           ` Ard Biesheuvel

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+Gu9uxXJMGMX0FG3Hx1Z-dukw2EtWYsJAh4iYcY5PLvj69A@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