From: "Laszlo Ersek" <lersek@redhat.com>
To: jejb@linux.ibm.com, Tom Lendacky <thomas.lendacky@amd.com>,
devel@edk2.groups.io
Cc: dovmurik@linux.vnet.ibm.com, Dov.Murik1@il.ibm.com,
ashish.kalra@amd.com, brijesh.singh@amd.com, tobin@ibm.com,
david.kaplan@amd.com, jon.grimm@amd.com, frankeh@us.ibm.com,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [PATCH v2 3/6] OvmfPkg: convert ES Reset Block structure to be guided
Date: Wed, 25 Nov 2020 00:19:27 +0100 [thread overview]
Message-ID: <c705952c-6d36-b404-fd17-9f8b907260e4@redhat.com> (raw)
In-Reply-To: <be404e70030795cbc21ff511f95a9247c1aa36db.camel@linux.ibm.com>
On 11/24/20 20:07, James Bottomley wrote:
> On Tue, 2020-11-24 at 08:57 -0600, Tom Lendacky wrote:
>> On 11/23/20 4:16 PM, Laszlo Ersek wrote:
>>> On 11/20/20 19:45, James Bottomley wrote:
>>>> Convert the current ES reset block structure to an extensible
>>>> guid based structure by appending a header and length, which
>>>> allow for multiple guid based data packets to be inserted.
>>
>> I was wondering if this patch should be submitted outside of this
>> series? I'm not sure it makes any difference, other than being able
>> to be merged (possibly) quicker and independent of the series. Then
>> this series simply takes advantage of it.
>
> How about if I shuffle it to the beginning of the series? That way it
> can be taken on its own or with the rest.
I wouldn't mind either approach in general; however, we're in hard
feature freeze now for edk2-stable202011 anyway, and I can't merge
anything resembling a new feature until after 2020-Nov-27.
https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Release-Planning
... Moving the patch to the front could still improve the structure /
build-up of the series, however. So yes, I guess please move it to the
front.
Cheers!
Laszlo
next prev parent reply other threads:[~2020-11-24 23:19 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-20 18:45 [PATCH v2 0/6] SEV Encrypted Boot for Ovmf James Bottomley
2020-11-20 18:45 ` [PATCH v2 1/6] OvmfPkg/Amdsev: Base commit to build encrypted boot specific OVMF James Bottomley
2020-11-23 18:01 ` Laszlo Ersek
2020-11-23 23:25 ` James Bottomley
2020-11-23 23:43 ` Laszlo Ersek
2020-11-20 18:45 ` [PATCH v2 2/6] OvmfPkg/AmdSev: add Grub Firmware Volume Package James Bottomley
2020-11-23 21:08 ` Laszlo Ersek
2020-11-24 6:38 ` James Bottomley
2020-11-24 8:23 ` Laszlo Ersek
2020-11-24 14:54 ` Laszlo Ersek
2020-11-24 15:58 ` Laszlo Ersek
2020-11-24 16:22 ` [edk2-devel] " James Bottomley
2020-11-24 23:22 ` Laszlo Ersek
2020-11-24 23:42 ` James Bottomley
2020-11-25 1:27 ` James Bottomley
2020-11-25 14:01 ` Laszlo Ersek
2020-11-25 16:02 ` James Bottomley
2020-11-25 17:09 ` James Bottomley
2020-11-25 18:17 ` James Bottomley
2020-11-25 19:20 ` Laszlo Ersek
2020-11-25 20:11 ` James Bottomley
2020-11-25 18:35 ` Laszlo Ersek
2020-11-25 19:08 ` Laszlo Ersek
2020-11-25 19:14 ` Laszlo Ersek
2020-11-20 18:45 ` [PATCH v2 3/6] OvmfPkg: convert ES Reset Block structure to be guided James Bottomley
2020-11-23 22:16 ` Laszlo Ersek
2020-11-24 14:57 ` Lendacky, Thomas
2020-11-24 19:07 ` James Bottomley
2020-11-24 23:19 ` Laszlo Ersek [this message]
2020-11-24 19:05 ` James Bottomley
2020-11-24 23:15 ` Laszlo Ersek
2020-11-20 18:45 ` [PATCH v2 4/6] OvmfPkg: create a SEV secret area in the AmdSev memfd James Bottomley
2020-11-23 22:28 ` Laszlo Ersek
2020-11-20 18:45 ` [PATCH v2 5/6] OvmfPkg/AmdSev: assign and protect the Sev Secret area James Bottomley
2020-11-23 22:38 ` Laszlo Ersek
2020-11-20 18:45 ` [PATCH v2 6/6] OvmfPkg/AmdSev: Expose the Sev Secret area using a configuration table James Bottomley
2020-11-23 22:56 ` Laszlo Ersek
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=c705952c-6d36-b404-fd17-9f8b907260e4@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