From: Thomas Huth <thuth@redhat.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>, qemu-devel@nongnu.org
Cc: Chen Huacai <zltjiangshi@gmail.com>,
Aleksandar Rikalo <aleksandar.rikalo@syrmia.com>,
Paul Burton <paulburton@kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Aurelien Jarno <aurelien@aurel32.net>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [PATCH v2 3/4] MAINTAINERS: Downgrade MIPS Boston to 'Odd Fixes', fix Paul Burton mail
Date: Wed, 14 Oct 2020 14:55:27 +0200 [thread overview]
Message-ID: <7ae71256-eebb-cba5-78ae-89e571cfdeb4@redhat.com> (raw)
In-Reply-To: <20201013101659.3557154-4-f4bug@amsat.org>
On 13/10/2020 12.16, Philippe Mathieu-Daudé wrote:
> Paul's Wavecomp email has been bouncing for months. He told us
> he "no longer has access to modern MIPS CPUs or Boston hardware,
> and wouldn't currently have time to spend on them if he did." [1]
> but "perhaps that might change in the future." [2].
> Be fair and downgrade the status of the Boston board to "Odd Fixes"
> (has a maintainer but they don't have time to do much other).
> Similarly to commit 2b107c2c1c (".mailmap: Update Paul Burton email
> address"), update his email address here too.
>
> [1] https://www.mail-archive.com/qemu-devel@nongnu.org/msg718739.html
> [1] https://www.mail-archive.com/qemu-devel@nongnu.org/msg728605.html
>
> Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
> ---
> v2: Squashed email address change (Thomas Huth)
> ---
> MAINTAINERS | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 2de5943e388..702f73823fc 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -1161,9 +1161,9 @@ S: Maintained
> F: hw/intc/loongson_liointc.c
>
> Boston
> -M: Paul Burton <pburton@wavecomp.com>
> +M: Paul Burton <paulburton@kernel.org>
> R: Aleksandar Rikalo <aleksandar.rikalo@syrmia.com>
> -S: Maintained
> +S: Odd Fixes
> F: hw/core/loader-fit.c
> F: hw/mips/boston.c
> F: hw/pci-host/xilinx-pcie.c
>
Reviewed-by: Thomas Huth <thuth@redhat.com>
next prev parent reply other threads:[~2020-10-14 12:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-13 10:16 [PATCH v2 0/4] MAINTAINERS: Update MIPS sections Philippe Mathieu-Daudé
2020-10-13 10:16 ` [PATCH v2 1/4] MAINTAINERS: Put myself forward for MIPS target Philippe Mathieu-Daudé
2020-10-14 11:41 ` Thomas Huth
2020-10-14 15:13 ` Jiaxun Yang
2020-10-14 15:41 ` Philippe Mathieu-Daudé
2020-10-13 10:16 ` [PATCH v2 2/4] MAINTAINERS: Remove duplicated Malta test entries Philippe Mathieu-Daudé
2020-10-14 12:54 ` Thomas Huth
2020-10-13 10:16 ` [PATCH v2 3/4] MAINTAINERS: Downgrade MIPS Boston to 'Odd Fixes', fix Paul Burton mail Philippe Mathieu-Daudé
2020-10-14 12:55 ` Thomas Huth [this message]
2020-10-13 10:16 ` [PATCH v2 4/4] MAINTAINERS: Move MIPS GIC timer files to Boston board section Philippe Mathieu-Daudé
2020-10-14 13:39 ` Thomas Huth
2020-10-16 13:43 ` Philippe Mathieu-Daudé
2020-10-16 13:45 ` [PATCH v2 0/4] MAINTAINERS: Update MIPS sections Philippe Mathieu-Daudé
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=7ae71256-eebb-cba5-78ae-89e571cfdeb4@redhat.com \
--to=thuth@redhat.com \
--cc=aleksandar.rikalo@syrmia.com \
--cc=aurelien@aurel32.net \
--cc=f4bug@amsat.org \
--cc=paulburton@kernel.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=zltjiangshi@gmail.com \
/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).