From: Peter Maydell <peter.maydell@linaro.org>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: "QEMU Developers" <qemu-devel@nongnu.org>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [Qemu-devel] [PATCH 1/6] target/arm: Implement ID_PFR2
Date: Tue, 30 Apr 2019 13:13:47 +0100 [thread overview]
Message-ID: <CAFEAcA_Uco_Uczy1Ut5RCETtXVxrRpEE35MKHv0mDPYZeFE-mQ@mail.gmail.com> (raw)
In-Reply-To: <20190223023957.18865-2-richard.henderson@linaro.org>
On Sat, 23 Feb 2019 at 02:40, Richard Henderson
<richard.henderson@linaro.org> wrote:
>
> This was defined at some point before ARMv8.4, and will
> shortly be used by new processor descriptions.
>
> Signed-off-by: Richard Henderson <richard.henderson@linaro.org>
> ---
> target/arm/cpu.h | 1 +
> target/arm/helper.c | 4 ++--
> 2 files changed, 3 insertions(+), 2 deletions(-)
Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
thanks
-- PMM
WARNING: multiple messages have this Message-ID (diff)
From: Peter Maydell <peter.maydell@linaro.org>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
"QEMU Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 1/6] target/arm: Implement ID_PFR2
Date: Tue, 30 Apr 2019 13:13:47 +0100 [thread overview]
Message-ID: <CAFEAcA_Uco_Uczy1Ut5RCETtXVxrRpEE35MKHv0mDPYZeFE-mQ@mail.gmail.com> (raw)
Message-ID: <20190430121347.A7rDyD5TYhquEmRZNsTi-9ywXTWk5nQG5ynBWU6hLE0@z> (raw)
In-Reply-To: <20190223023957.18865-2-richard.henderson@linaro.org>
On Sat, 23 Feb 2019 at 02:40, Richard Henderson
<richard.henderson@linaro.org> wrote:
>
> This was defined at some point before ARMv8.4, and will
> shortly be used by new processor descriptions.
>
> Signed-off-by: Richard Henderson <richard.henderson@linaro.org>
> ---
> target/arm/cpu.h | 1 +
> target/arm/helper.c | 4 ++--
> 2 files changed, 3 insertions(+), 2 deletions(-)
Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
thanks
-- PMM
next prev parent reply other threads:[~2019-04-30 12:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-23 2:39 [Qemu-devel] [PATCH+RFC 0/6] target/arm: Define cortex-a{73, 75, 76} Richard Henderson
2019-02-23 2:39 ` [Qemu-devel] [PATCH 1/6] target/arm: Implement ID_PFR2 Richard Henderson
2019-04-30 12:13 ` Peter Maydell [this message]
2019-04-30 12:13 ` Peter Maydell
2019-02-23 2:39 ` [Qemu-devel] [PATCH 2/6] target/arm: Define cortex-a73 Richard Henderson
2019-04-30 12:23 ` Peter Maydell
2019-04-30 12:23 ` Peter Maydell
2019-02-23 2:39 ` [Qemu-devel] [PATCH 3/6] target/arm: Implement ID_AA64MMFR2 Richard Henderson
2019-04-30 12:25 ` Peter Maydell
2019-04-30 12:25 ` Peter Maydell
2019-02-23 2:39 ` [Qemu-devel] [RFC 4/6] target/arm: Define cortex-a75 Richard Henderson
2019-04-30 12:52 ` Peter Maydell
2019-04-30 12:52 ` Peter Maydell
2019-02-23 2:39 ` [Qemu-devel] [RFC 5/6] target/arm: Conditionalize DBGDIDR vs ID_AA64DFR0_EL1 assert Richard Henderson
2019-04-30 12:40 ` Peter Maydell
2019-04-30 12:40 ` Peter Maydell
2019-02-23 2:39 ` [Qemu-devel] [RFC 6/6] target/arm: Define cortex-a76 Richard Henderson
2019-04-30 12:57 ` [Qemu-devel] [PATCH+RFC 0/6] target/arm: Define cortex-a{73, 75, 76} Peter Maydell
2019-04-30 12:57 ` Peter Maydell
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=CAFEAcA_Uco_Uczy1Ut5RCETtXVxrRpEE35MKHv0mDPYZeFE-mQ@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).