From: Palmer Dabbelt <palmer@dabbelt.com>
To: jeffreyalaw@gmail.com
Cc: juzhe.zhong@rivai.ai, gcc-patches@gcc.gnu.org,
Kito Cheng <kito.cheng@gmail.com>
Subject: Re: [PATCH] RISC-V: Fix incorrect annotation
Date: Tue, 20 Dec 2022 08:06:31 -0800 (PST) [thread overview]
Message-ID: <mhng-d79ac133-2f09-4029-a6a5-8112805bedbe@palmer-ri-x1c9> (raw)
In-Reply-To: <07263860-511a-2611-620f-76fe97350033@gmail.com>
On Tue, 20 Dec 2022 08:02:56 PST (-0800), jeffreyalaw@gmail.com wrote:
>
>
> On 12/19/22 17:38, juzhe.zhong wrote:
>> Would you mind merging it for me？ I can‘t merge code.
> Do you mean you do not have write access to the repository? If so, that
> can be easily fixed.
>
> https://sourceware.org/cgi-bin/pdw/ps_form.cgi
>
> List me as your sponsor.
Do we also need to add him to the write after approval section in
MAINTAINERS? We were trying to remember how to do this on IRC last
night...
next prev parent reply other threads:[~2022-12-20 16:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-19 23:13 juzhe.zhong
2022-12-20 0:28 ` Jeff Law
[not found] ` <36D1C05330B9612D+065D340F-26F5-4844-8ACE-EA8091A41E6A@rivai.ai>
2022-12-20 16:02 ` Jeff Law
2022-12-20 16:06 ` Palmer Dabbelt [this message]
2022-12-20 16:15 ` Jeff Law
2022-12-20 23:33 ` 钟居哲
2022-12-20 23:38 ` Palmer Dabbelt
2022-12-23 5:47 ` Kito Cheng
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=mhng-d79ac133-2f09-4029-a6a5-8112805bedbe@palmer-ri-x1c9 \
--to=palmer@dabbelt.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=juzhe.zhong@rivai.ai \
--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).