From: "Laszlo Ersek" <lersek@redhat.com>
To: Leif Lindholm <leif@nuviainc.com>, Abner Chang <abner.chang@hpe.com>
Cc: devel@edk2.groups.io, Andrew Fish <afish@apple.com>,
Michael D Kinney <michael.d.kinney@intel.com>,
Leif Lindholm <leif.lindholm@linaro.org>
Subject: Re: [PATCH 1/1] Maintainers.txt: Update reviewers of */RiscV64
Date: Mon, 31 Aug 2020 10:58:03 +0200 [thread overview]
Message-ID: <a6d046e4-9b4d-cd0b-d8a2-702271ac0e04@redhat.com> (raw)
In-Reply-To: <20200830114401.GB20124@vanye>
On 08/30/20 13:44, Leif Lindholm wrote:
> On Sun, Aug 30, 2020 at 16:03:06 +0800, Abner Chang wrote:
>> Add reviewers for all /RiscV64 folders.
>>
>> Signed-off-by: Abner Chang <abner.chang@hpe.com>
>> 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: Leif Lindholm <leif.lindholm@linaro.org>
>> ---
>> Maintainers.txt | 5 +++++
>> 1 file changed, 5 insertions(+)
>>
>> diff --git a/Maintainers.txt b/Maintainers.txt
>> index 57cd2fc662..ff34a24abd 100644
>> --- a/Maintainers.txt
>> +++ b/Maintainers.txt
>> @@ -98,6 +98,11 @@ F: */Arm/
>> M: Leif Lindholm <leif@nuviainc.com>
>> M: Ard Biesheuvel <ard.biesheuvel@arm.com>
>>
>> +RISCV64
>> +F: */RiscV64/
>> +R: Abner Chang <abner.chang@hpe.com>
>> +R: Daniel Schaefer <daniel.schaefer@hpe.com>
>
> I think we want an M: entry for this, and I think that should be you
> (since you have the access privileges). It signifies that you are the
> one responsible for patches that have been reviewed actually get
> pushed.
>
> This doesn't always mean you need to do it yourself, especially for
> this entry which will always overlap with other entries (like MdePkg,
> MdeModulePkg, ...), but it does make it clear that you need to make
> sure it doesn't get dropped.
>
> With that change:
> Reviewed-by: Leif Lindholm <leif@nuviainc.com>
>
>> +
>> EDK II Continuous Integration:
>> ------------------------------
>> .azurepipelines/
>> --
>> 2.25.0
>>
>
The placement and the contents of the addition look good to me. I don't
know what the best approach is regarding R vs M.
With or without the modification suggested by Leif:
Acked-by: Laszlo Ersek <lersek@redhat.com>
Thanks
Laszlo
prev parent reply other threads:[~2020-08-31 8:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-30 8:03 [PATCH 1/1] Maintainers.txt: Update reviewers of */RiscV64 Abner Chang
2020-08-30 11:44 ` Leif Lindholm
2020-08-30 13:00 ` Abner Chang
2020-08-31 8:58 ` 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=a6d046e4-9b4d-cd0b-d8a2-702271ac0e04@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