From: Jeff Law <jeffreyalaw@gmail.com>
To: "juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai>,
"pan2.li" <pan2.li@intel.com>,
gcc-patches <gcc-patches@gcc.gnu.org>
Cc: Robin Dapp <rdapp.gcc@gmail.com>,
"yanzhang.wang" <yanzhang.wang@intel.com>,
"kito.cheng" <kito.cheng@gmail.com>
Subject: Re: [PATCH v2] RISC-V: Bugfix for RVV integer reduction in ZVE32/64.
Date: Fri, 16 Jun 2023 09:55:32 -0600 [thread overview]
Message-ID: <9c1beddd-6324-cf2c-b58f-461f4909d735@gmail.com> (raw)
In-Reply-To: <FD915B33E157789D+20230616161053815056102@rivai.ai>
On 6/16/23 02:10, juzhe.zhong@rivai.ai wrote:
> LGTM. Thanks for fix this bug.
> Let's wait for Jeff's final approve.
OK.
jeff
next prev parent reply other threads:[~2023-06-16 15:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-16 7:28 [PATCH v1] " pan2.li
2023-06-16 7:47 ` juzhe.zhong
2023-06-16 7:56 ` Li, Pan2
2023-06-16 8:09 ` [PATCH v2] " pan2.li
2023-06-16 8:10 ` juzhe.zhong
2023-06-16 8:16 ` Li, Pan2
2023-06-16 15:55 ` Jeff Law [this message]
2023-06-16 23:38 ` Li, Pan2
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=9c1beddd-6324-cf2c-b58f-461f4909d735@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=juzhe.zhong@rivai.ai \
--cc=kito.cheng@gmail.com \
--cc=pan2.li@intel.com \
--cc=rdapp.gcc@gmail.com \
--cc=yanzhang.wang@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).