public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Brijesh Singh <brijesh.singh@amd.com>
To: Tom Lendacky <thomas.lendacky@amd.com>,
	Laszlo Ersek <lersek@redhat.com>, Min Xu <min.m.xu@intel.com>,
	Jiewen Yao <jiewen.yao@intel.com>,
	James Bottomley <jejb@linux.ibm.com>
Cc: brijesh.singh@amd.com, devel@edk2.groups.io,
	Andrew Fish <afish@apple.com>, Leif Lindholm <leif@nuviainc.com>,
	Michael D Kinney <michael.d.kinney@intel.com>
Subject: Re: [PATCH 2/2] Maintainers.txt: Add reviewers for Confidential Computing related modules
Date: Wed, 10 Mar 2021 09:29:28 -0600	[thread overview]
Message-ID: <b355cfaf-67f9-b8a3-4deb-5277743c544c@amd.com> (raw)
In-Reply-To: <6a1a50d3-5d87-6150-762c-4f320e358109@amd.com>


On 3/10/21 9:09 AM, Tom Lendacky wrote:
> On 3/10/21 8:20 AM, Laszlo Ersek wrote:
>> Adding James, Brijesh, Tom; comments below:
>>
>> On 03/10/21 03:55, Min Xu wrote:
>>> Register reviewers for the Confidential Computing related modules 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>
>>> ---
>
> ...
>
>>
>> So... can we simply rename the current SEV subsystem to "Confidential
>> Computing", and keep both TDX and SEV modules under it? We could place a
>> unified email address list there, with Brijesh, James, Jiewen, Min, Tom.
>>
>> I don't think this should cause any confusion, because:
>>
>> - @intel.com emails are clearly closely associated with TDX, and
>> @amd.com emails are clearly closely associated with SEV,
>>
>> - most filenames will (or do already) include "AmdSev" or "Tdx",
>>
>> - future patches should clearly label themselves as "SEV only", "TDX
>> only", or "confidential computing in general" -- this should be clear
>> from the patch subjects.
>>
>> IOW, there should be no confusion as to who's required to review what,
>> but at the same time we'd have a simple solution for cross-posting all
>> interested parties.
>>
>> Thoughts?
>
> Works for me.


Works for me as well.


  reply	other threads:[~2021-03-10 15:29 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
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 [this message]
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=b355cfaf-67f9-b8a3-4deb-5277743c544c@amd.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