From: Peter Maydell <peter.maydell@linaro.org>
To: qemu-devel@nongnu.org
Subject: [PULL 0/2] target-arm queue
Date: Mon, 8 Apr 2024 16:23:44 +0100 [thread overview]
Message-ID: <20240408152346.3937318-1-peter.maydell@linaro.org> (raw)
Two bug fixes for 9.0...
-- PMM
The following changes since commit ce64e6224affb8b4e4b019f76d2950270b391af5:
Merge tag 'qemu-sparc-20240404' of https://github.com/mcayland/qemu into staging (2024-04-04 15:28:06 +0100)
are available in the Git repository at:
https://git.linaro.org/people/pmaydell/qemu-arm.git tags/pull-target-arm-20240408
for you to fetch changes up to 19b254e86a900dc5ee332e3ac0baf9c521301abf:
target/arm: Use correct SecuritySpace for AArch64 AT ops at EL3 (2024-04-08 15:38:53 +0100)
----------------------------------------------------------------
target-arm:
* Use correct SecuritySpace for AArch64 AT ops at EL3
* Fix CNTPOFF_EL2 trap to missing EL3
----------------------------------------------------------------
Peter Maydell (1):
target/arm: Use correct SecuritySpace for AArch64 AT ops at EL3
Pierre-Clément Tosi (1):
target/arm: Fix CNTPOFF_EL2 trap to missing EL3
target/arm/helper.c | 10 +++++++---
1 file changed, 7 insertions(+), 3 deletions(-)
next reply other threads:[~2024-04-08 15:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-08 15:23 Peter Maydell [this message]
2024-04-08 15:23 ` [PULL 1/2] target/arm: Fix CNTPOFF_EL2 trap to missing EL3 Peter Maydell
2024-04-08 15:23 ` [PULL 2/2] target/arm: Use correct SecuritySpace for AArch64 AT ops at EL3 Peter Maydell
2024-04-09 8:47 ` [PULL 0/2] target-arm queue Peter Maydell
-- strict thread matches above, loose matches on Subject: below --
2023-04-10 14:14 Peter Maydell
2023-04-10 18:45 ` Peter Maydell
2022-11-22 16:39 Peter Maydell
2022-11-22 20:36 ` Stefan Hajnoczi
2022-04-05 9:26 Peter Maydell
2022-04-05 13:01 ` Peter Maydell
2022-03-25 14:57 Peter Maydell
2022-03-26 10:19 ` Peter Maydell
2020-08-04 16:08 Peter Maydell
2020-08-04 18:45 ` 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=20240408152346.3937318-1-peter.maydell@linaro.org \
--to=peter.maydell@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.