From: Robin Dapp <rdapp.gcc@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: rdapp.gcc@gmail.com, jeffreyalaw <jeffreyalaw@gmail.com>,
"yanzhang.wang" <yanzhang.wang@intel.com>,
"kito.cheng" <kito.cheng@gmail.com>
Subject: Re: [PATCH v1] RISC-V: Fix one typo in full-vec-movel test
Date: Tue, 13 Jun 2023 09:23:58 +0200 [thread overview]
Message-ID: <893f28c0-6b74-ccf8-b288-218b9399225e@gmail.com> (raw)
In-Reply-To: <98DCBE5722CBB81C+2023061315215503183416@rivai.ai>
> Oh. Sorry. Since I want to commit my patch so I asked Pan to commit
> your test as well. I think you can resend a fix of this testcase and
> drop this patch.
No problem, will fix it another time. Pan can just go ahead with this
fix now, no need to wait for a maintainer, it's obvious enough.
Thanks
Robin
next prev parent reply other threads:[~2023-06-13 7:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-13 7:17 pan2.li
2023-06-13 7:20 ` Robin Dapp
2023-06-13 7:21 ` juzhe.zhong
2023-06-13 7:23 ` Robin Dapp [this message]
2023-06-13 7:27 ` 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=893f28c0-6b74-ccf8-b288-218b9399225e@gmail.com \
--to=rdapp.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=juzhe.zhong@rivai.ai \
--cc=kito.cheng@gmail.com \
--cc=pan2.li@intel.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).