From: "Laszlo Ersek" <lersek@redhat.com>
To: Abner Chang <abner.chang@hpe.com>, devel@edk2.groups.io
Cc: Andrew Fish <afish@apple.com>, Leif Lindholm <leif@nuviainc.com>,
Michael D Kinney <michael.d.kinney@intel.com>,
Leif Lindholm <leif.lindholm@linaro.org>
Subject: Re: [PATCH v2 1/1] Maintainers.txt: Update reviewers of */RiscV64
Date: Fri, 4 Sep 2020 10:25:20 +0200 [thread overview]
Message-ID: <a8d3e27e-8d7b-57b0-ecdb-aa10803fab0d@redhat.com> (raw)
In-Reply-To: <20200904071913.17295-1-abner.chang@hpe.com>
On 09/04/20 09:19, 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>
> Acked-by: Laszlo Ersek <lersek@redhat.com>
> ---
> Maintainers.txt | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/Maintainers.txt b/Maintainers.txt
> index 57cd2fc662..6a22a14796 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/
> +M: Abner Chang <abner.chang@hpe.com>
> +R: Daniel Schaefer <daniel.schaefer@hpe.com>
> +
> EDK II Continuous Integration:
> ------------------------------
> .azurepipelines/
>
What are the changes relative to v1?
(Also, I believe Leif is away at the moment, and I think we should have
his ACK on this patch, before we merge the patch.)
Thanks
Laszlo
next prev parent reply other threads:[~2020-09-04 8:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-04 7:19 [PATCH v2 1/1] Maintainers.txt: Update reviewers of */RiscV64 Abner Chang
2020-09-04 8:25 ` Laszlo Ersek [this message]
2020-09-04 8:51 ` Abner Chang
2020-09-04 9:43 ` Laszlo Ersek
2020-09-04 10:07 ` Abner Chang
2020-09-04 10:04 ` [edk2-devel] " Laszlo Ersek
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=a8d3e27e-8d7b-57b0-ecdb-aa10803fab0d@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