From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>,
qemu-arm@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH 0/6] target/arm: Move feature tests to their own header
Date: Tue, 24 Oct 2023 18:50:22 +0200 [thread overview]
Message-ID: <dcba89fa-fb3c-711d-acbe-9dfce9b89c0f@linaro.org> (raw)
In-Reply-To: <20231024163510.2972081-1-peter.maydell@linaro.org>
On 24/10/23 18:35, Peter Maydell wrote:
> Peter Maydell (6):
> target/arm: Move feature test functions to their own header
> target/arm: Move ID_AA64MMFR1 and ID_AA64MMFR2 tests together
> target/arm: Move ID_AA64MMFR0 tests up to before MMFR1 and MMFR2
> target/arm: Move ID_AA64ISAR* test functions together
> target/arm: Move ID_AA64PFR* tests together
> target/arm: Move ID_AA64DFR* feature tests together
Series:
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
prev parent reply other threads:[~2023-10-24 16:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-24 16:35 [PATCH 0/6] target/arm: Move feature tests to their own header Peter Maydell
2023-10-24 16:35 ` [PATCH 1/6] target/arm: Move feature test functions " Peter Maydell
2023-10-25 23:34 ` Richard Henderson
2023-10-24 16:35 ` [PATCH 2/6] target/arm: Move ID_AA64MMFR1 and ID_AA64MMFR2 tests together Peter Maydell
2023-10-25 23:34 ` Richard Henderson
2023-10-24 16:35 ` [PATCH 3/6] target/arm: Move ID_AA64MMFR0 tests up to before MMFR1 and MMFR2 Peter Maydell
2023-10-25 23:35 ` Richard Henderson
2023-10-24 16:35 ` [PATCH 4/6] target/arm: Move ID_AA64ISAR* test functions together Peter Maydell
2023-10-25 23:35 ` Richard Henderson
2023-10-24 16:35 ` [PATCH 5/6] target/arm: Move ID_AA64PFR* tests together Peter Maydell
2023-10-25 23:36 ` Richard Henderson
2023-10-24 16:35 ` [PATCH 6/6] target/arm: Move ID_AA64DFR* feature " Peter Maydell
2023-10-25 23:36 ` Richard Henderson
2023-10-24 16:50 ` Philippe Mathieu-Daudé [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=dcba89fa-fb3c-711d-acbe-9dfce9b89c0f@linaro.org \
--to=philmd@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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 NNTP newsgroup(s).