From: "Laszlo Ersek" <lersek@redhat.com>
To: Leif Lindholm <leif@nuviainc.com>
Cc: edk2-devel-groups-io <devel@edk2.groups.io>,
"Andrew Fish" <afish@apple.com>,
"Ard Biesheuvel" <ardb+tianocore@kernel.org>,
"Brijesh Singh" <brijesh.singh@amd.com>,
"James Bottomley" <jejb@linux.ibm.com>,
"Jiewen Yao" <jiewen.yao@intel.com>,
"Jordan Justen" <jordan.l.justen@intel.com>,
"Michael D Kinney" <michael.d.kinney@intel.com>,
"Min Xu" <min.m.xu@intel.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Tom Lendacky" <thomas.lendacky@amd.com>
Subject: Re: [PATCH 0/2] Maintainers: create the "OvmfPkg: Confidential Computing" subsystem
Date: Thu, 11 Mar 2021 15:14:38 +0100 [thread overview]
Message-ID: <008a3fc6-2b24-719b-b2c4-f60b0ba63a12@redhat.com> (raw)
In-Reply-To: <20210311113354.GO1664@vanye>
On 03/11/21 12:33, Leif Lindholm wrote:
> If I was feeling spectacularly nitpicky, I'd grumble something about
> 2/2 smashing several logical changes into one. But this is a small
> update to Maintainers.txt rather than code, so ... for the series.
>
> Acked-by: Leif Lindholm <leif@nuviainc.com>
Thanks -- and yes, I did consider splitting those, but the linkage
between each step is quite strong. Without TDX, I have no reason to
rename the section; once I hint at TDX, I need to add Intel reviewers; I
can't add Intel reviewers well without sorting the current "R:" list;
once I rename the section, I need to move it... Not impossible to split,
but it would have resulted in 5-6 patches, each with ~3 lines.
Thanks for accepting the patch.
Laszlo
>
> On Wed, Mar 10, 2021 at 19:56:47 +0100, Laszlo Ersek wrote:
>> Ref: https://bugzilla.tianocore.org/show_bug.cgi?id=2198
>> Ref: https://bugzilla.tianocore.org/show_bug.cgi?id=3077
>> Ref: https://bugzilla.tianocore.org/show_bug.cgi?id=3249
>>
>> Generalize the current OVMF SEV subsystem entry, so that we can use it
>> for Intel TDX in the future, ensuring proper patch circulation for
>> reviews.
>>
>> Cc: Andrew Fish <afish@apple.com>
>> Cc: Ard Biesheuvel <ardb+tianocore@kernel.org>
>> Cc: Brijesh Singh <brijesh.singh@amd.com>
>> Cc: James Bottomley <jejb@linux.ibm.com>
>> Cc: Jiewen Yao <jiewen.yao@intel.com>
>> Cc: Jordan Justen <jordan.l.justen@intel.com>
>> Cc: Leif Lindholm <leif@nuviainc.com>
>> Cc: Michael D Kinney <michael.d.kinney@intel.com>
>> Cc: Min Xu <min.m.xu@intel.com>
>> Cc: Philippe Mathieu-Daudé <philmd@redhat.com>
>> Cc: Tom Lendacky <thomas.lendacky@amd.com>
>>
>> Thanks
>> Laszlo
>>
>> Laszlo Ersek (2):
>> Maintainers: refresh the OVMF SEV subsystem after TianoCore #2198 and
>> #3077
>> Maintainers: rename the OVMF SEV subsystem to "Confidential Computing"
>>
>> Maintainers.txt | 28 +++++++++++++-------
>> 1 file changed, 18 insertions(+), 10 deletions(-)
>>
>>
>> base-commit: edd46cd407ea4a0adaa8d6ca86f550c2a4d5c507
>> --
>> 2.19.1.3.g30247aa5d201
>>
>
next prev parent reply other threads:[~2021-03-11 14:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 18:56 [PATCH 0/2] Maintainers: create the "OvmfPkg: Confidential Computing" subsystem Laszlo Ersek
2021-03-10 18:56 ` [PATCH 1/2] Maintainers: refresh the OVMF SEV subsystem after TianoCore #2198 and #3077 Laszlo Ersek
2021-03-10 18:56 ` [PATCH 2/2] Maintainers: rename the OVMF SEV subsystem to "Confidential Computing" Laszlo Ersek
2021-03-10 19:20 ` [edk2-devel] [PATCH 0/2] Maintainers: create the "OvmfPkg: Confidential Computing" subsystem Ard Biesheuvel
2021-03-10 19:22 ` Philippe Mathieu-Daudé
2021-03-10 22:06 ` Brijesh Singh
2021-03-10 22:27 ` Lendacky, Thomas
2021-03-11 0:40 ` [edk2-devel] " Yao, Jiewen
2021-03-11 11:33 ` Leif Lindholm
2021-03-11 14:14 ` Laszlo Ersek [this message]
2021-03-11 17:13 ` [edk2-devel] " Laszlo Ersek
2021-03-11 17:15 ` James Bottomley
2021-03-18 0:13 ` Laszlo Ersek
2021-03-18 8:36 ` Min Xu
2021-03-18 18:14 ` 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=008a3fc6-2b24-719b-b2c4-f60b0ba63a12@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