From: YunQiang Su <yunqiang.su@cipunited.com>
To: gcc-patches@gcc.gnu.org
Cc: richard.sandiford@arm.com, jeffreyalaw@gmail.com,
YunQiang Su <yunqiang.su@cipunited.com>
Subject: [COMMITTED] MAINTAINERS: Add myself as MIPS port maintainer
Date: Fri, 2 Jun 2023 10:10:59 +0800 [thread overview]
Message-ID: <20230602021059.2229464-1-yunqiang.su@cipunited.com> (raw)
ChangeLog:
* MAINTAINERS (CPU Port Maintainers): Add myself as MIPS
port maintainer.
(Write After Approval): Remove myself.
---
MAINTAINERS | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 4a7c963914b..c8b787b6e1e 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -91,7 +91,7 @@ m68k port Andreas Schwab <schwab@linux-m68k.org>
m68k-motorola-sysv port Philippe De Muyter <phdm@macqel.be>
mcore port Nick Clifton <nickc@redhat.com>
microblaze Michael Eager <eager@eagercon.com>
-mips port Matthew Fortune <mfortune@gmail.com>
+mips port YunQiang Su <yunqiang.su@cipunited.com>
mmix port Hans-Peter Nilsson <hp@bitrange.com>
mn10300 port Jeff Law <jeffreyalaw@gmail.com>
mn10300 port Alexandre Oliva <aoliva@gcc.gnu.org>
@@ -652,7 +652,6 @@ Basile Starynkevitch <basile@starynkevitch.net>
Jakub Staszak <kuba@et.pl>
Graham Stott <graham.stott@btinternet.com>
Jeff Sturm <jsturm@gcc.gnu.org>
-YunQiang Su <yunqiang.su@cipunited.com>
Robert Suchanek <rsuchy84@gmail.com>
Andrew Sutton <andrew.n.sutton@gmail.com>
Gabriele Svelto <gabriele.svelto@st.com>
--
2.30.2
next reply other threads:[~2023-06-02 2:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 2:10 YunQiang Su [this message]
2023-06-03 14:51 ` Maciej W. Rozycki
2023-06-04 17:33 ` Matthew Fortune
2023-06-05 1:50 ` [PATCH] MAINTAINERS: move Matthew Fortune to Write After Approval YunQiang Su
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=20230602021059.2229464-1-yunqiang.su@cipunited.com \
--to=yunqiang.su@cipunited.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=richard.sandiford@arm.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 read-only IMAP folder(s) and NNTP newsgroup(s).