From: Kito Cheng <kito.cheng@gmail.com>
To: Jeff Law <jeffreyalaw@gmail.com>
Cc: 钟居哲 <juzhe.zhong@rivai.ai>,
"GCC Patches" <gcc-patches@gcc.gnu.org>,
"Palmer Dabbelt" <palmer@dabbelt.com>
Subject: Re: [PATCH] RISC-V: Fix annotation
Date: Mon, 19 Dec 2022 23:07:33 +0800 [thread overview]
Message-ID: <CA+yXCZDq9YwUyC7H5DfLxng8Rh_-CBCfFa2BM6Qic+gX=C9r3Q@mail.gmail.com> (raw)
In-Reply-To: <3e604bc2-4ce3-c665-a6c5-549785b8afe5@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 399 bytes --]
Merged into previou patch.
Jeff Law via Gcc-patches <gcc-patches@gcc.gnu.org> 於 2022年12月17日 週六 03:54
寫道:
>
>
> On 12/14/22 01:39, juzhe.zhong@rivai.ai wrote:
> > From: Ju-Zhe Zhong <juzhe.zhong@rivai.ai>
> >
> > gcc/ChangeLog:
> >
> > * config/riscv/riscv-vsetvl.cc: Fix annotation.
> Just roll this into the patch that adds riscv-vsetvl.cc.
>
> jeff
>
next prev parent reply other threads:[~2022-12-19 15:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-14 8:39 juzhe.zhong
2022-12-16 19:53 ` Jeff Law
2022-12-19 15:07 ` Kito Cheng [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-08-30 2:57 juzhe.zhong
2022-09-01 2:05 ` Kito Cheng
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='CA+yXCZDq9YwUyC7H5DfLxng8Rh_-CBCfFa2BM6Qic+gX=C9r3Q@mail.gmail.com' \
--to=kito.cheng@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=juzhe.zhong@rivai.ai \
--cc=palmer@dabbelt.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).