Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: Zenghui Yu <yuzenghui@huawei.com>
Cc: torvalds@linux-foundation.org, catalin.marinas@arm.com,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, kernel-team@android.com,
	brauner@kernel.org
Subject: Re: [GIT PULL] arm64 updates for 6.18
Date: Wed, 1 Oct 2025 10:42:40 +0100	[thread overview]
Message-ID: <aNz3kLEOA60pdRmH@willie-the-truck> (raw)
In-Reply-To: <4016897f-42a5-bb18-4ebb-80de97f99a60@huawei.com>

On Sun, Sep 28, 2025 at 07:27:17PM +0800, Zenghui Yu wrote:
> On 2025/9/27 1:13, Will Deacon wrote:
> > ACPI, EFI and PSCI:
> >  - Decouple Arm's "Software Delegated Exception Interface" (SDEI)
> >    support from the ACPI GHES code so that it can be used by platforms
> >    booted with device-tree.
> > 
> >  - Remove unnecessary per-CPU tracking of the FPSIMD state across EFI
> >    runtime calls.
> > 
> >  - Fix a node refcount imbalance in the PSCI device-tree code.
> > 
> > CPU Features:
> >  - Ensure register sanitisation is applied to fields in ID_AA64MMFR4.
> > 
> >  - Expose AIDR_EL1 to userspace via sysfs, primarily so that KVM guests
> >    can reliably query the underlying CPU types from the VMM.
> > 
> >  - Re-enabling of SME support (CONFIG_ARM64_SME) as a result of fixes
> >    to our context-switching, signal handling and ptrace code.
> 
> IIRC they're 6.16 stuff [*].
> 
> [*] https://lore.kernel.org/all/20250528114103.GA27965@willie-the-truck

Well spotted! It's nice to see eagle-eyed review of the tag summary. In
this case, I forgot to drop a couple of sections from the previous tag I
wrote -- we use the same tag name each time ("arm64-upstream"), so it
gets pre-filled with the old contents when we update it and, since
Catalin and I take it in turns, that's why 6.16 showed up here.

The good news is that the actual pull request is fine and Linus has
already pulled it. I now wonder how many quality news sites will report
that arm64 is re-enabling SME in 6.18 ;)

Will


  reply	other threads:[~2025-10-01  9:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-26 17:13 [GIT PULL] arm64 updates for 6.18 Will Deacon
2025-09-28 11:27 ` Zenghui Yu
2025-10-01  9:42   ` Will Deacon [this message]
2025-09-30  2:54 ` pr-tracker-bot

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=aNz3kLEOA60pdRmH@willie-the-truck \
    --to=will@kernel.org \
    --cc=brauner@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=kernel-team@android.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=yuzenghui@huawei.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