From: Jeff Law <jeffreyalaw@gmail.com>
To: Patrick O'Neill <patrick@rivosinc.com>, gcc-patches@gcc.gnu.org
Cc: kito.cheng@gmail.com, gnu-toolchain@rivosinc.com
Subject: Re: [PATCH 0/3] RISC-V: Amo testsuite cleanup
Date: Wed, 12 Jun 2024 12:12:00 -0600 [thread overview]
Message-ID: <35e86b32-5761-4ff2-a1ca-927be8d00265@gmail.com> (raw)
In-Reply-To: <20240611180342.2420602-1-patrick@rivosinc.com>
On 6/11/24 12:03 PM, Patrick O'Neill wrote:
> This series moves the atomic-related riscv testcases into their own folder and
> fixes some minor bugs/rigidity of existing testcases.
This series is OK.
jeff
next prev parent reply other threads:[~2024-06-12 18:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-11 18:03 Patrick O'Neill
2024-06-11 18:03 ` [PATCH 1/3] RISC-V: Move amo tests into subfolder Patrick O'Neill
2024-06-11 18:03 ` [PATCH 2/3] RISC-V: Fix amoadd call arguments Patrick O'Neill
2024-06-11 18:03 ` [PATCH 3/3] RISC-V: Allow any temp register to be used in amo tests Patrick O'Neill
2024-06-12 18:12 ` Jeff Law [this message]
2024-06-12 18:20 ` [Committed] RISC-V: Amo testsuite cleanup Patrick O'Neill
2024-06-25 21:14 [PATCH 0/3] RISC-V: AMO " Patrick O'Neill
2024-06-25 21:34 ` Jeff Law
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=35e86b32-5761-4ff2-a1ca-927be8d00265@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gnu-toolchain@rivosinc.com \
--cc=kito.cheng@gmail.com \
--cc=patrick@rivosinc.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).