From: "Li, Pan2" <pan2.li@intel.com>
To: Jeff Law <jeffreyalaw@gmail.com>,
"juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai>,
Robin Dapp <rdapp.gcc@gmail.com>,
gcc-patches <gcc-patches@gcc.gnu.org>
Cc: Kito.cheng <kito.cheng@sifive.com>, palmer <palmer@rivosinc.com>
Subject: RE: [PATCH] RISC-V: Fix V_WHOLE && V_FRACT iterator requirement
Date: Tue, 13 Jun 2023 01:28:33 +0000 [thread overview]
Message-ID: <MW5PR11MB5908B9E4C6A318603AF6A45EA955A@MW5PR11MB5908.namprd11.prod.outlook.com> (raw)
In-Reply-To: <04e2b487-165f-747d-9e9e-0826dbdf6a30@gmail.com>
Committed, thanks Jeff.
Pan
-----Original Message-----
From: Gcc-patches <gcc-patches-bounces+pan2.li=intel.com@gcc.gnu.org> On Behalf Of Jeff Law via Gcc-patches
Sent: Tuesday, June 13, 2023 3:54 AM
To: juzhe.zhong@rivai.ai; Robin Dapp <rdapp.gcc@gmail.com>; gcc-patches <gcc-patches@gcc.gnu.org>
Cc: Kito.cheng <kito.cheng@sifive.com>; palmer <palmer@rivosinc.com>
Subject: Re: [PATCH] RISC-V: Fix V_WHOLE && V_FRACT iterator requirement
On 6/12/23 03:58, juzhe.zhong@rivai.ai wrote:
> I'd like you to defer to you commit my patch with your test (Jeff has
> approved my patch, just feel free to commit).
Then let's go with that. Juzhe's patch + Robin's test.
jeff
prev parent reply other threads:[~2023-06-13 1:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 14:32 juzhe.zhong
2023-06-09 14:37 ` Robin Dapp
2023-06-09 14:40 ` 钟居哲
2023-06-09 14:42 ` Robin Dapp
2023-06-09 14:45 ` Jeff Law
2023-06-09 23:50 ` 钟居哲
2023-06-12 9:51 ` Robin Dapp
2023-06-12 9:58 ` juzhe.zhong
2023-06-12 12:27 ` Kito Cheng
2023-06-12 19:53 ` Jeff Law
2023-06-13 1:28 ` Li, Pan2 [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=MW5PR11MB5908B9E4C6A318603AF6A45EA955A@MW5PR11MB5908.namprd11.prod.outlook.com \
--to=pan2.li@intel.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=juzhe.zhong@rivai.ai \
--cc=kito.cheng@sifive.com \
--cc=palmer@rivosinc.com \
--cc=rdapp.gcc@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).