From: Thomas Huth <thuth@redhat.com>
To: Aleksandar Markovic <aleksandar.qemu.devel@gmail.com>,
qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, "Aurelien Jarno" <aurelien@aurel32.net>,
"Magnus Damm" <magnus.damm@gmail.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Yoshinori Sato" <ysato@users.sourceforge.jp>
Subject: Re: [PATCH v3 1/1] MAINTAINERS: Adjust sh4 maintainership
Date: Thu, 11 Jun 2020 13:15:45 +0200 [thread overview]
Message-ID: <505493ed-02c5-2760-5def-ce5a74b7cdd3@redhat.com> (raw)
In-Reply-To: <20200611095316.10133-2-aleksandar.qemu.devel@gmail.com>
On 11/06/2020 11.53, Aleksandar Markovic wrote:
> This patch transfers sh4 sections to Yoshinori Sato, who is
> best positioned in the community to assume sh4 maintainership.
> He is the maintainer of the related target rx as well, which
> means that some synergy between the two targets can be expected
> in future.
>
> Further adjustments, reorganizations, and improvements of sh4
> sections are left to the future maintainer to be devised and
> executed, as he deems suitable.
>
> Aurelien and Magnus are deleted as maintainers in some sections
> of the MAINTAINERS file with this patch. However, they will not
> be deleted from QEMU Hall of Fame, where their names will always
> remained carved in stone as QEMU pioneers and granddaddies.
>
> Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
> Acked-by: Aurelien Jarno <aurelien@aurel32.net>
> Acked-by: Magnus Damm <magnus.damm@gmail.com>
> Acked-by: Yoshinori Sato <ysato@users.sourceforge.jp>
> Signed-off-by: Aleksandar Markovic <aleksandar.qemu.devel@gmail.com>
> ---
> MAINTAINERS | 8 +++++---
> 1 file changed, 5 insertions(+), 3 deletions(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 6e7890ce82..5c78ff5672 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -296,7 +296,7 @@ F: tests/tcg/s390x/
> L: qemu-s390x@nongnu.org
>
> SH4 TCG CPUs
> -M: Aurelien Jarno <aurelien@aurel32.net>
> +M: Yoshinori Sato <ysato@users.sourceforge.jp>
> S: Odd Fixes
> F: target/sh4/
> F: hw/sh4/
> @@ -1251,14 +1251,16 @@ F: include/hw/riscv/opentitan.h
> SH4 Machines
> ------------
> R2D
> -M: Magnus Damm <magnus.damm@gmail.com>
> +M: Yoshinori Sato <ysato@users.sourceforge.jp>
> +R: Magnus Damm <magnus.damm@gmail.com>
> S: Maintained
> F: hw/sh4/r2d.c
> F: hw/intc/sh_intc.c
> F: hw/timer/sh_timer.c
>
> Shix
> -M: Magnus Damm <magnus.damm@gmail.com>
> +M: Yoshinori Sato <ysato@users.sourceforge.jp>
> +R: Magnus Damm <magnus.damm@gmail.com>
> S: Odd Fixes
> F: hw/sh4/shix.c
Reviewed-by: Thomas Huth <thuth@redhat.com>
next prev parent reply other threads:[~2020-06-11 11:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 9:53 [PATCH v3 0/1] Resolution of sh4 maintainership Aleksandar Markovic
2020-06-11 9:53 ` [PATCH v3 1/1] MAINTAINERS: Adjust " Aleksandar Markovic
2020-06-11 11:15 ` Thomas Huth [this message]
2020-06-15 19:13 ` Aleksandar Markovic
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-all 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=505493ed-02c5-2760-5def-ce5a74b7cdd3@redhat.com \
--to=thuth@redhat.com \
--cc=aleksandar.qemu.devel@gmail.com \
--cc=aurelien@aurel32.net \
--cc=f4bug@amsat.org \
--cc=magnus.damm@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=ysato@users.sourceforge.jp \
/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;
as well as URLs for NNTP newsgroup(s).