From: "Li, Pan2" <pan2.li@intel.com>
To: Jeff Law <jeffreyalaw@gmail.com>,
"juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai>,
Li Xu <xuli1@eswincomputing.com>,
gcc-patches <gcc-patches@gcc.gnu.org>
Cc: kito.cheng <kito.cheng@gmail.com>, palmer <palmer@dabbelt.com>,
zhengyu <zhengyu@eswincomputing.com>
Subject: RE: [PATCH v2] RISC-V: fix expand function of vlmul_ext RVV intrinsic
Date: Sun, 25 Jun 2023 14:06:02 +0000 [thread overview]
Message-ID: <MW5PR11MB5908C4771D773EB6B8F60BCFA921A@MW5PR11MB5908.namprd11.prod.outlook.com> (raw)
In-Reply-To: <f2b4ed71-288a-9948-310f-952552f71ee5@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: Sunday, June 25, 2023 8:55 PM
To: juzhe.zhong@rivai.ai; Li Xu <xuli1@eswincomputing.com>; gcc-patches <gcc-patches@gcc.gnu.org>
Cc: kito.cheng <kito.cheng@gmail.com>; palmer <palmer@dabbelt.com>; zhengyu <zhengyu@eswincomputing.com>
Subject: Re: [PATCH v2] RISC-V: fix expand function of vlmul_ext RVV intrinsic
On 6/25/23 03:13, juzhe.zhong@rivai.ai wrote:
> LGTM.
> Thanks for fixing it.
Agreed. I didn't see the V2 had already been posted.
>
> Hi, Jeff:
> I saw Li Xu is frequently helping RVV support in GCC. Is it possible to
> give him the write access?
Yes, we can do that with the normal process.
Li Xu, fill out this form:
https://sourceware.org/cgi-bin/pdw/ps_form.cgi
List me as approving the request.
Jeff
next prev parent reply other threads:[~2023-06-25 14:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-25 9:09 Li Xu
2023-06-25 9:13 ` juzhe.zhong
2023-06-25 12:54 ` Jeff Law
2023-06-25 14:06 ` Li, Pan2 [this message]
2023-06-26 9:16 ` Li Xu
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=MW5PR11MB5908C4771D773EB6B8F60BCFA921A@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@gmail.com \
--cc=palmer@dabbelt.com \
--cc=xuli1@eswincomputing.com \
--cc=zhengyu@eswincomputing.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).