From: Jeff Law <jeffreyalaw@gmail.com>
To: 钟居哲 <juzhe.zhong@rivai.ai>, gcc-patches <gcc-patches@gcc.gnu.org>
Cc: "kito.cheng" <kito.cheng@gmail.com>, palmer <palmer@dabbelt.com>
Subject: Re: [GCC14 QUEUE PATCH] RISC-V: Optimize fault only first load
Date: Mon, 24 Apr 2023 17:47:16 -0600 [thread overview]
Message-ID: <59d8a6a5-daed-51d0-e053-1d59c94e7855@gmail.com> (raw)
In-Reply-To: <49286AE822D679E8+202304240658519556531@rivai.ai>
On 4/23/23 16:58, 钟居哲 wrote:
> Hi, Jeff.
> I have fixed patches as you suggested:
> https://gcc.gnu.org/pipermail/gcc-patches/2023-April/616515.html
> <https://gcc.gnu.org/pipermail/gcc-patches/2023-April/616515.html>
> https://gcc.gnu.org/pipermail/gcc-patches/2023-April/616518.html
> <https://gcc.gnu.org/pipermail/gcc-patches/2023-April/616518.html>
> https://gcc.gnu.org/pipermail/gcc-patches/2023-April/616516.html
> <https://gcc.gnu.org/pipermail/gcc-patches/2023-April/616516.html>
>
> Can you merge these patches?
I would really prefer you get to the point where you're committing your
own patches. I'm already quite overloaded and having to apply your
patches isn't going to help.
I'm willing to invest some time to address concerns/problems you may
have with the commit flow as that ultimately makes both of us more
effective. But I really don't have the time to sit here and push patches.
So let's start with the basics. Have you applied for and received
write permissions? If so, add yourself to the MAINTAINERS file. If
not, please fill out this form:
> https://sourceware.org/cgi-bin/pdw/ps_form.cgi
Jeff
prev parent reply other threads:[~2023-04-24 23:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 1:28 juzhe.zhong
2023-04-22 3:18 ` Jeff Law
2023-04-23 22:58 ` 钟居哲
2023-04-24 23:47 ` Jeff Law [this message]
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=59d8a6a5-daed-51d0-e053-1d59c94e7855@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=juzhe.zhong@rivai.ai \
--cc=kito.cheng@gmail.com \
--cc=palmer@dabbelt.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).