Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: torvalds@linux-foundation.org
Cc: catalin.marinas@arm.com, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, kernel-team@android.com
Subject: [GIT PULL] arm64 fixes for 6.18
Date: Tue, 25 Nov 2025 16:12:12 +0000	[thread overview]
Message-ID: <aSXVXLWDyDguHgiA@willie-the-truck> (raw)

Hi Linus,

Apologies for sending this during the US holidays but please can you
pull these three straightforward arm64 fixes for 6.18?

We've got a revert due to one of the recent CCA commits breaking ACPI
firmware-based error reporting, a fix for a hard-lockup introduced by a
prior fix affecting non-default (CONFIG_EXPERT) configurations and
another ACPI fix for systems using MMIO-based timers.

Other than that, we're looking pretty good.

Cheers,

Will

--->8

The following changes since commit 8e8ae788964aa2573b4335026db4068540fa6a86:

  arm64: Reject modules with internal alternative callbacks (2025-11-07 15:00:14 +0000)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git tags/arm64-fixes

for you to fetch changes up to 165eb13e485c5c25c7cb276ac85f788a2bd200cb:

  arm64: proton-pack: Fix hard lockup when !MITIGATE_SPECTRE_BRANCH_HISTORY (2025-11-24 13:31:50 +0000)

----------------------------------------------------------------
arm64 fixes for 6.18

- Avoid hardlockup when CONFIG_MITIGATE_SPECTRE_BRANCH_HISTORY=n

- Fix regression in APEI/GHES error handling

- Fix MMIO timers when probed via ACPI

----------------------------------------------------------------
Jonathan Marek (1):
      arm64: proton-pack: Fix hard lockup when !MITIGATE_SPECTRE_BRANCH_HISTORY

Marc Zyngier (1):
      ACPI: GTDT: Correctly number platform devices for MMIO timers

Will Deacon (1):
      Revert "arm64: acpi: Enable ACPI CCEL support"

 arch/arm64/kernel/acpi.c        | 10 ----------
 arch/arm64/kernel/proton-pack.c |  2 ++
 drivers/acpi/arm64/gtdt.c       |  4 ++--
 3 files changed, 4 insertions(+), 12 deletions(-)


             reply	other threads:[~2025-11-25 16:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-25 16:12 Will Deacon [this message]
2025-11-25 16:39 ` [GIT PULL] arm64 fixes for 6.18 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=aSXVXLWDyDguHgiA@willie-the-truck \
    --to=will@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 \
    /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