From: "juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai>
To: demin.han <demin.han@starfivetech.com>,
gcc-patches <gcc-patches@gcc.gnu.org>
Cc: kito.cheng <kito.cheng@gmail.com>
Subject: Re: [PATCH] MAINTAINERS: Add myself to write after approval
Date: Wed, 6 Mar 2024 10:12:40 +0800 [thread overview]
Message-ID: <CDEAA2D3A0945496+202403061012402934196@rivai.ai> (raw)
In-Reply-To: <20240304065105.1706971-1-demin.han@starfivetech.com>
[-- Attachment #1: Type: text/plain, Size: 976 bytes --]
Hi, han.
I think you can commit this patch:
https://gcc.gnu.org/pipermail/gcc-patches/2024-March/646931.html
RISC-V: Refactor expand_vec_cmp
It's an NFC patch that I approved.
juzhe.zhong@rivai.ai
From: demin.han
Date: 2024-03-04 14:51
To: gcc-patches
CC: juzhe.zhong; kito.cheng
Subject: [PATCH] MAINTAINERS: Add myself to write after approval
ChangeLog:
* MAINTAINERS: Add myself
Signed-off-by: demin.han <demin.han@starfivetech.com>
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index b01fab16061..a681518d704 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -448,6 +448,7 @@ Wei Guozhi <carrot@google.com>
Vineet Gupta <vineetg@rivosinc.com>
Naveen H.S <naveenh@marvell.com>
Mostafa Hagog <hagog@gcc.gnu.org>
+Demin Han <demin.han@starfivetech.com>
Jivan Hakobyan <jivanhakobyan9@gmail.com>
Andrew Haley <aph@redhat.com>
Frederik Harwath <frederik@harwath.name>
--
2.43.2
next prev parent reply other threads:[~2024-03-06 2:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 6:51 demin.han
2024-03-06 2:12 ` juzhe.zhong [this message]
2024-03-06 10:22 ` Demin Han
-- strict thread matches above, loose matches on Subject: below --
2023-09-18 9:52 Fei Gao
2023-08-25 23:42 Edwin Lu
2023-05-31 8:29 P Jeevitha
2023-05-11 3:13 juzhe.zhong
2023-04-26 16:07 Patrick O'Neill
2023-04-26 16:08 ` Palmer Dabbelt
2023-04-25 9:46 [PATCH] MAINTAINERS: add " Victor L. Do Nascimento
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=CDEAA2D3A0945496+202403061012402934196@rivai.ai \
--to=juzhe.zhong@rivai.ai \
--cc=demin.han@starfivetech.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=kito.cheng@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 read-only IMAP folder(s) and NNTP newsgroup(s).