From: Richard Sandiford <richard.sandiford@arm.com>
To: "juzhe.zhong\@rivai.ai" <juzhe.zhong@rivai.ai>
Cc: rguenther <rguenther@suse.de>, gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH V6] VECT: Add SELECT_VL support
Date: Fri, 09 Jun 2023 18:44:11 +0100 [thread overview]
Message-ID: <mptwn0cjztg.fsf@arm.com> (raw)
In-Reply-To: <E6945E4B4FF8632D+202306091916467397112@rivai.ai> (juzhe's message of "Fri, 9 Jun 2023 19:16:47 +0800")
"juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai> writes:
> Thanks, Richi.
>
> Should I wait for Richard ACK gain ?
> Since the last email of this patch, he just asked me to adjust comment no codes change.
> I am not sure whether he is ok.
Yeah, OK from my POV too, thanks.
Richard
next prev parent reply other threads:[~2023-06-09 17:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 8:39 juzhe.zhong
2023-06-09 9:20 ` juzhe.zhong
2023-06-09 11:02 ` Richard Biener
2023-06-09 11:16 ` juzhe.zhong
2023-06-09 17:44 ` Richard Sandiford [this message]
2023-06-09 23:54 ` Li, Pan2
2023-06-09 11:32 ` juzhe.zhong
2023-06-09 14:42 ` Jeff Law
2023-06-09 14:43 ` 钟居哲
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=mptwn0cjztg.fsf@arm.com \
--to=richard.sandiford@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=juzhe.zhong@rivai.ai \
--cc=rguenther@suse.de \
/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).