From: Richard Henderson <richard.henderson@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Subject: Re: [PULL v2 00/32] target-arm queue
Date: Sun, 31 Aug 2025 09:07:19 +1000 [thread overview]
Message-ID: <dfaa2800-f132-4a46-9751-2d9fb38c5bef@linaro.org> (raw)
In-Reply-To: <20250830160828.3593075-1-peter.maydell@linaro.org>
On 8/31/25 02:08, Peter Maydell wrote:
> v2: handle bsd-user in the rename of isar_feature_aa64_atomics
>
> -- PMM
>
> The following changes since commit 4791f22a5f5571cb248b1eddff98630545b3fd3e:
>
> Merge tag 'pull-lu-20250830' ofhttps://gitlab.com/rth7680/qemu into staging (2025-08-30 08:24:48 +1000)
>
> are available in the Git repository at:
>
> https://gitlab.com/pm215/qemu.git tags/pull-target-arm-20250830
>
> for you to fetch changes up to 2e27650bddd35477d994a795a3b1cb57c8ed5c76:
>
> hw/arm/stm32f205_soc: Don't leak TYPE_OR_IRQ objects (2025-08-30 16:38:47 +0100)
>
> ----------------------------------------------------------------
> target-arm queue:
> * Implement FEAT_SCTLR2
> * Implement FEAT_TCR2
> * Implement FEAT_CSSC
> * Implement FEAT_LSE128
> * Clean up of register field definitions
> * Trap PMCR when MDCR_EL2.TPMCR is set
> * tests/functional: update aarch64 RME test images
> * hw/intc/arm_gicv3_kvm: preserve pending interrupts during cpr
> * hw/arm: add static NVDIMMs in device tree
> * hw/arm/stm32f205_soc: Don't leak TYPE_OR_IRQ objects
> * scripts/kernel-doc: Avoid new Perl precedence warning
> * scripts/kernel-doc: Update to kernel's new Python implementation
Applied, thanks. Please update https://wiki.qemu.org/ChangeLog/10.2 as appropriate.
r~
next prev parent reply other threads:[~2025-08-30 23:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-30 16:08 [PULL v2 00/32] target-arm queue Peter Maydell
2025-08-30 23:07 ` Richard Henderson [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-09-14 15:02 Peter Maydell
2020-09-14 18:22 ` 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=dfaa2800-f132-4a46-9751-2d9fb38c5bef@linaro.org \
--to=richard.henderson@linaro.org \
--cc=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 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).