From: 钟居哲 <juzhe.zhong@rivai.ai>
To: "Jeff Law" <jeffreyalaw@gmail.com>,
demin.han <demin.han@starfivetech.com>,
gcc-patches <gcc-patches@gcc.gnu.org>
Cc: pan2.li <pan2.li@intel.com>
Subject: Re: Re: [PATCH] RISC-V: Fix calculation of max live vregs
Date: Wed, 20 Dec 2023 23:30:49 +0800 [thread overview]
Message-ID: <4A3B18EE6D7FECEE+2023122023304905543944@rivai.ai> (raw)
In-Reply-To: <1f44e02c-fffe-4150-86d0-c0e696ae0ec8@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 829 bytes --]
Ok. Thanks Jeff reminding me.
Will be carefull next time.
juzhe.zhong@rivai.ai
From: Jeff Law
Date: 2023-12-20 23:28
To: juzhe.zhong@rivai.ai; demin.han; gcc-patches
CC: pan2.li
Subject: Re: [PATCH] RISC-V: Fix calculation of max live vregs
On 12/20/23 04:17, juzhe.zhong@rivai.ai wrote:
> I see. LGTM. Thanks for explanation.
>
> I will ask Li Pan commit it for you.
The patch from Demin didn't specify if it had been regression tested.
All patches must be regression tested and an indication that the test
passed and on what target must be included in the patch email thread.
Please don't ACK patches that haven't followed this policy. It's OK with
conditions like "OK after verifying this patch doesn't cause regressions
in the testsuite on rv64gc" or something similar.
jeff
next prev parent reply other threads:[~2023-12-20 15:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-20 8:15 demin.han
2023-12-20 9:56 ` juzhe.zhong
2023-12-20 11:10 ` Demin Han
2023-12-20 11:17 ` juzhe.zhong
2023-12-20 11:20 ` Li, Pan2
2023-12-20 15:28 ` Jeff Law
2023-12-20 15:30 ` 钟居哲 [this message]
2023-12-21 1:47 ` Demin Han
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=4A3B18EE6D7FECEE+2023122023304905543944@rivai.ai \
--to=juzhe.zhong@rivai.ai \
--cc=demin.han@starfivetech.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=pan2.li@intel.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).