From: "Laszlo Ersek" <lersek@redhat.com>
To: devel@edk2.groups.io, ray.ni@intel.com
Cc: Andrew Fish <afish@apple.com>, "Dong, Eric" <eric.dong@intel.com>,
Gerd Hoffmann <kraxel@redhat.com>,
Leif Lindholm <quic_llindhol@quicinc.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>,
"Kumar, Rahul R" <rahul.r.kumar@intel.com>
Subject: Re: [edk2-devel] [PATCH 1/1] Maintainers.txt: designate Gerd Hoffmann as UefiCpuPkg reviewer
Date: Fri, 6 Jan 2023 09:21:55 +0100 [thread overview]
Message-ID: <e220b28b-e70a-9c6e-217b-5266b6a31e01@redhat.com> (raw)
In-Reply-To: <MN6PR11MB82440E25C6A38E332C2C75488CF59@MN6PR11MB8244.namprd11.prod.outlook.com>
On 1/4/23 15:06, Ni, Ray wrote:
> Reviewed-by: Ray Ni <ray.ni@intel.com>
Thanks; PR#3861 / commit 0aca5901e344.
Laszlo
>
>> -----Original Message-----
>> From: Laszlo Ersek <lersek@redhat.com>
>> Sent: Wednesday, January 4, 2023 12:06 AM
>> To: devel@edk2.groups.io
>> Cc: Andrew Fish <afish@apple.com>; Dong, Eric <eric.dong@intel.com>; Gerd Hoffmann <kraxel@redhat.com>; Leif
>> Lindholm <quic_llindhol@quicinc.com>; Kinney, Michael D <michael.d.kinney@intel.com>; Kumar, Rahul R
>> <rahul.r.kumar@intel.com>; Ni, Ray <ray.ni@intel.com>
>> Subject: [PATCH 1/1] Maintainers.txt: designate Gerd Hoffmann as UefiCpuPkg reviewer
>>
>> I suggest that Gerd be notified about all UefiCpuPkg patches, so he may
>> take a quick look at, or (by his preference) even test, the proposed
>> change, in a genuine QEMU/KVM environment.
>>
>> Assuming this patch is accepted -- subsequently, please *wait* for Gerd's
>> approval on UefiCpuPkg patches, before merging them.
>>
>> Notes:
>>
>> - It's perfectly fine for a reviewer to give an A-b just so the review
>> process be unblocked, if they don't have anything to add, or don't have
>> time to review or test in detail. The point is that someone outside of
>> Intel should *consistently get a chance* to raise concerns about
>> UefiCpuPkg patches before they are merged.
>>
>> - My A-b's and R-b's on UefiCpuPkg patches were never supposed to be
>> "sufficient", only "necessary", for merging. The intent is the same
>> here, with Gerd's designation as a reviewer.
>>
>> Cc: Andrew Fish <afish@apple.com>
>> Cc: Eric Dong <eric.dong@intel.com>
>> Cc: Gerd Hoffmann <kraxel@redhat.com>
>> Cc: Leif Lindholm <quic_llindhol@quicinc.com>
>> Cc: Michael D Kinney <michael.d.kinney@intel.com>
>> Cc: Rahul Kumar <rahul1.kumar@intel.com>
>> Cc: Ray Ni <ray.ni@intel.com>
>> Signed-off-by: Laszlo Ersek <lersek@redhat.com>
>> ---
>> Maintainers.txt | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/Maintainers.txt b/Maintainers.txt
>> index 13e1335a57dd..3399981bbae7 100644
>> --- a/Maintainers.txt
>> +++ b/Maintainers.txt
>> @@ -605,6 +605,7 @@ W: https://github.com/tianocore/tianocore.github.io/wiki/UefiCpuPkg
>> M: Eric Dong <eric.dong@intel.com> [ydong10]
>> M: Ray Ni <ray.ni@intel.com> [niruiyu]
>> R: Rahul Kumar <rahul1.kumar@intel.com> [rahul1-kumar]
>> +R: Gerd Hoffmann <kraxel@redhat.com> [kraxel]
>>
>> UefiCpuPkg: Sec related modules
>> F: UefiCpuPkg/SecCore/
>
>
>
>
>
prev parent reply other threads:[~2023-01-06 8:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-03 16:05 [PATCH 1/1] Maintainers.txt: designate Gerd Hoffmann as UefiCpuPkg reviewer Laszlo Ersek
2023-01-04 11:21 ` Gerd Hoffmann
2023-01-04 14:06 ` Ni, Ray
2023-01-06 8:21 ` Laszlo Ersek [this message]
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=e220b28b-e70a-9c6e-217b-5266b6a31e01@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