From: "Laszlo Ersek" <lersek@redhat.com>
To: Min Xu <min.m.xu@intel.com>, devel@edk2.groups.io
Cc: Andrew Fish <afish@apple.com>, Leif Lindholm <leif@nuviainc.com>,
Michael D Kinney <michael.d.kinney@intel.com>,
Jiewen Yao <jiewen.yao@intel.com>
Subject: Re: [PATCH 1/2] Maintainers.txt: Add reviewers for the OvmfPkg TDX-related files
Date: Wed, 10 Mar 2021 14:20:09 +0100 [thread overview]
Message-ID: <3c11e766-0172-9482-d5a6-268c413fdc01@redhat.com> (raw)
In-Reply-To: <d11c1ed8-646d-1e3d-5cf7-92458b7e4baf@redhat.com>
On 03/10/21 14:12, Laszlo Ersek wrote:
> On 03/10/21 03:55, Min Xu wrote:
>> Register reviewers for the TDX-related files in OvmfPkg.
>>
>> Cc: Andrew Fish <afish@apple.com>
>> Cc: Laszlo Ersek <lersek@redhat.com>
>> Cc: Leif Lindholm <leif@nuviainc.com>
>> Cc: Michael D Kinney <michael.d.kinney@intel.com>
>> Cc: Jiewen Yao <jiewen.yao@intel.com>
>> Signed-off-by: Min Xu <min.m.xu@intel.com>
>> ---
>> Maintainers.txt | 4 ++++
>> 1 file changed, 4 insertions(+)
>>
>> diff --git a/Maintainers.txt b/Maintainers.txt
>> index e38497123857..7d9fe89d6d28 100644
>> --- a/Maintainers.txt
>> +++ b/Maintainers.txt
>> @@ -465,6 +465,10 @@ F: OvmfPkg/PlatformPei/AmdSev.c
>> R: Tom Lendacky <thomas.lendacky@amd.com>
>> R: Brijesh Singh <brijesh.singh@amd.com>
>>
>> +OvmfPkg: TDX-related modules
>> +R: Jiewen Yao <jiewen.yao@intel.com>
>> +R: Min Xu <min.m.xu@intel.com>
>> +
>> OvmfPkg: TCG- and TPM2-related modules
>> F: OvmfPkg/Include/IndustryStandard/QemuTpm.h
>> F: OvmfPkg/Library/PlatformBootManagerLib/BdsPlatform.c
>>
>
> I'm OK with the patch content, however the placement of the new section
> is not right. We strive to keep the section headers alphabetically
> ordered. Here's an excerpt (pre-patch):
>
> OvmfPkg: SEV-related modules
> OvmfPkg: TCG- and TPM2-related modules
> OvmfPkg: Xen-related modules
>
> I think that the new section belongs between TCG and Xen.
Also -- I actually forgot the more important issue -- this patch does
not add any pathname patterns that the section is supposed to apply to!
Please refer to the "F:" patterns in the "Maintainers.txt" file, both
the explanation near the top of the file, and the various OvmfPkg examples.
And then, given that there are no TDX-related files in the tree at the
moment (so no F: pattern makes sense at the moment), I think adding this
section is premature. This patch should become part of your initial
TdxLib contribution -- the patch could be the last one in your series,
covering the pathnames introduced by the previous patches in your
series. So (just an example) we might have something like:
OvmfPkg: TDX-related modules
F: OvmfPkg/Library/TdxLib/
R: Jiewen Yao <jiewen.yao@intel.com>
R: Min Xu <min.m.xu@intel.com>
Subsequently to that, every time you introduced a new TDX-related module
(library instance, lib class header, driver, ...), you'd add matching
"F:" patterns to the above subsystem.
Thanks
Laszlo
next prev parent reply other threads:[~2021-03-10 13:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 2:55 [PATCH 0/2] Update Maintainers.txt for TDX and Confidential Computing Min Xu
2021-03-10 2:55 ` [PATCH 1/2] Maintainers.txt: Add reviewers for the OvmfPkg TDX-related files Min Xu
2021-03-10 13:12 ` Laszlo Ersek
2021-03-10 13:20 ` Laszlo Ersek [this message]
2021-03-10 2:55 ` [PATCH 2/2] Maintainers.txt: Add reviewers for Confidential Computing related modules Min Xu
2021-03-10 14:20 ` Laszlo Ersek
2021-03-10 15:09 ` Lendacky, Thomas
2021-03-10 15:29 ` Brijesh Singh
2021-03-10 15:33 ` James Bottomley
2021-03-10 17:04 ` [edk2-devel] " Yao, Jiewen
2021-03-10 3:03 ` [PATCH 0/2] Update Maintainers.txt for TDX and Confidential Computing Yao, Jiewen
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=3c11e766-0172-9482-d5a6-268c413fdc01@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