From: "Lehua Ding" <lehua.ding@rivai.ai>
To: 钟居哲 <juzhe.zhong@rivai.ai>, gcc-patches <gcc-patches@gcc.gnu.org>
Cc: "Jeff Law" <jeffreyalaw@gmail.com>, "pan2.li" <pan2.li@intel.com>
Subject: Re: [PATCH V2] RISC-V: Remove duplicate `#include "riscv-vector-switch.def"`
Date: Tue, 13 Jun 2023 19:07:32 +0800 [thread overview]
Message-ID: <tencent_5E11DF2C3F6D68C72C4C48BE@qq.com> (raw)
In-Reply-To: <0D0074E35140CBB1+2023061318595644772220@rivai.ai>
[-- Attachment #1: Type: text/plain, Size: 113 bytes --]
> LGTM.
> Thanks.
> Will merge it soon.
Thank you for such a prompt reply.
prev parent reply other threads:[~2023-06-13 11:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-13 10:59 Lehua Ding
2023-06-13 10:59 ` juzhe.zhong
2023-06-13 11:07 ` Lehua Ding [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=tencent_5E11DF2C3F6D68C72C4C48BE@qq.com \
--to=lehua.ding@rivai.ai \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=juzhe.zhong@rivai.ai \
--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).