From: Robin Dapp <rdapp.gcc@gmail.com>
To: "Li, Pan2" <pan2.li@intel.com>,
"juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai>,
gcc-patches <gcc-patches@gcc.gnu.org>
Cc: rdapp.gcc@gmail.com, jeffreyalaw <jeffreyalaw@gmail.com>,
"Wang, Yanzhang" <yanzhang.wang@intel.com>,
"kito.cheng" <kito.cheng@gmail.com>
Subject: Re: [PATCH v1] RISC-V: Fix one typo of FRM dynamic definition
Date: Mon, 3 Jul 2023 16:56:33 +0200 [thread overview]
Message-ID: <3ba88be2-4f5d-b70c-ddb3-b7d7e0c5a445@gmail.com> (raw)
In-Reply-To: <MW5PR11MB590803DBFC3AD6D1D1F89B6FA929A@MW5PR11MB5908.namprd11.prod.outlook.com>
> Sorry for inconvenient, still working on fix it. If urgent I can
> revert this change to unblock your work ASAP.
I'm not blocked by this, thanks, just wanted to document it here.
I was testing another patch and needed to dig for a while until
I realized the FAILs come from this one. In general I would
assume that even obvious patches are tested before (I have
introduced bugs by obvious ones before so I make sure to).
Regards
Robin
next prev parent reply other threads:[~2023-07-03 14:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 8:08 pan2.li
2023-07-03 8:09 ` juzhe.zhong
2023-07-03 8:14 ` Robin Dapp
2023-07-03 8:17 ` Li, Pan2
2023-07-03 14:49 ` Robin Dapp
2023-07-03 14:53 ` Li, Pan2
2023-07-03 14:56 ` Robin Dapp [this message]
2023-07-03 14:59 ` Li, Pan2
2023-07-04 3:21 ` Li, Pan2
2023-07-04 13:14 ` Robin Dapp
2023-07-04 13:18 ` 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=3ba88be2-4f5d-b70c-ddb3-b7d7e0c5a445@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).