public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Laszlo Ersek" <lersek@redhat.com>
To: devel@edk2.groups.io, eric.dong@intel.com
Cc: Jiewen Yao <jiewen.yao@intel.com>,
	Jian J Wang <jian.j.wang@intel.com>,
	Chao Zhang <chao.b.zhang@intel.com>, Min Xu <min.m.xu@intel.com>
Subject: Re: [edk2-devel] [PATCH 2/5] Maintainers.txt: Add reviewer for security boot modules.
Date: Wed, 3 Jun 2020 17:02:40 +0200	[thread overview]
Message-ID: <851c4c47-979a-cc69-3517-5beaa6cf49e3@redhat.com> (raw)
In-Reply-To: <ef2bf4ca-3d5e-e6af-0cce-562a90460b0b@redhat.com>

On 06/03/20 16:57, Laszlo Ersek wrote:
> On 06/03/20 05:18, Dong, Eric wrote:
>> Signed-off-by: Eric Dong <eric.dong@intel.com>
>> Cc: Jiewen Yao <jiewen.yao@intel.com>
>> Cc: Jian J Wang <jian.j.wang@intel.com>
>> Cc: Chao Zhang <chao.b.zhang@intel.com>
>> Cc: Min Xu <min.m.xu@intel.com>
>> ---
>>  Maintainers.txt | 6 ++++++
>>  1 file changed, 6 insertions(+)
>>
>> diff --git a/Maintainers.txt b/Maintainers.txt
>> index 954dc567e0..573084e086 100644
>> --- a/Maintainers.txt
>> +++ b/Maintainers.txt
>> @@ -458,6 +458,12 @@ F: SecurityPkg/Tcg/
>>  R: Qi Zhang <qi1.zhang@intel.com>
>>  R: Rahul Kumar <rahul1.kumar@intel.com>
>>  
>> +SecurityPkg: Secure boot related modules
>> +F: SecurityPkg/Library/DxeImageVerificationLib/
>> +F: SecurityPkg/VariableAuthenticated/SecureBootConfigDxe/
>> +F: SecurityPkg/Library/AuthVariableLib/
>> +R: Min Xu <min.m.xu@intel.com>
>> +
>>  ShellPkg
>>  F: ShellPkg/
>>  W: https://github.com/tianocore/tianocore.github.io/wiki/ShellPkg
>>
> 
> (1) please replace "security boot" with "secure boot" in the subject.
> 
> with that fixed:
> 
> Acked-by: Laszlo Ersek <lersek@redhat.com>
> 

(2) If I remember correctly, we originally wanted the section headers in
the Maintainers.txt file to remain alphabetically sorted.

This patch would create disorder:

SecurityPkg: Tcg related modules
SecurityPkg: Secure boot related modules

Therefore please add the "SecurityPkg: Secure boot related modules"
section above the "SecurityPkg: Tcg related modules" section.

With (1) and (2) fixed:

Acked-by: Laszlo Ersek <lersek@redhat.com>

(Now I do realize there is already some disorder in the Maintainers.txt
file; I'll post a patch for fixing the OvmfPkg-related ones.)

Thanks
Laszlo


  reply	other threads:[~2020-06-03 15:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-03  3:18 [PATCH 0/5] Add reviewers for security related modules Dong, Eric
2020-06-03  3:18 ` [PATCH 1/5] Maintainers.txt: Add reviewers for Tcg " Dong, Eric
2020-06-03 14:53   ` [edk2-devel] " Laszlo Ersek
2020-06-08  3:35   ` Wang, Jian J
2020-06-03  3:18 ` [PATCH 2/5] Maintainers.txt: Add reviewer for security boot modules Dong, Eric
2020-06-03 14:57   ` [edk2-devel] " Laszlo Ersek
2020-06-03 15:02     ` Laszlo Ersek [this message]
2020-06-08  3:36       ` Wang, Jian J
2020-06-03  3:18 ` [PATCH 3/5] Maintainers.txt: Add reviewer for UefiCpuPkg Dong, Eric
2020-06-03 14:58   ` [edk2-devel] " Laszlo Ersek
2020-06-03  3:18 ` [PATCH 4/5] Maintainers.txt: Add reviewer for SEC related modules Dong, Eric
2020-06-03 14:59   ` [edk2-devel] " Laszlo Ersek
2020-06-03  3:18 ` [PATCH 5/5] Maintainers.txt: Add reviewer for Pei Core Dong, Eric
2020-06-03 15:05   ` [edk2-devel] " Laszlo Ersek
2020-06-08  3:38   ` Wang, Jian J

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=851c4c47-979a-cc69-3517-5beaa6cf49e3@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