All of lore.kernel.org
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Will Deacon <will@kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: [GIT PULL] arm64 fixes for 7.1-rc2
Date: Fri, 1 May 2026 22:15:06 +0100	[thread overview]
Message-ID: <afUX2gRwmgEfU0X1@arm.com> (raw)

Hi Linus,

Please pull the arm64 fixes below. Thanks.

The following changes since commit 254f49634ee16a731174d2ae34bc50bd5f45e731:

  Linux 7.1-rc1 (2026-04-26 14:19:00 -0700)

are available in the Git repository at:

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

for you to fetch changes up to 030e8a40fff65ca6ac1c04a4d3c08afe72438922:

  arm64: signal: Preserve POR_EL0 if poe_context is missing (2026-05-01 17:44:25 +0100)

----------------------------------------------------------------
Assorted arm64, ACPI and kselftest fixes for 7.1-rc2:

 - Avoid writing an uninitialised stack variable to POR_EL0 on
   sigreturn if the poe_context record is absent

 - Reserve one more page for the early 4K-page kernel mapping to cover
   the extra [_text, _stext) split introduced by the non-executable
   read-only mapping

 - Force the arch_local_irq_*() wrappers to be __always_inline so that
   noinstr entry and idle paths cannot call out-of-line, instrumentable
   copies

 - Fix potential sign extension in the arm64 SCS unwinder's DWARF
   advance_loc4 decoding

 - Tolerate arm64 ACPI platforms with only WFI and no deeper PSCI idle
   states, restoring cpuidle registration on such systems

 - Include the UAPI <asm/ptrace.h> header in the arm64 GCS libc test
   rather than carrying a duplicate struct user_gcs definition (the
   original #ifdef NT_ARM_GCS was wrong to cover the structure
   definition as it would be masked out if the toolchain defined it)

----------------------------------------------------------------
Breno Leitao (2):
      arm64/irqflags: __always_inline the arch_local_irq_*() helpers
      ACPI: arm64: cpuidle: Tolerate platforms with no deep PSCI idle states

Kevin Brodsky (1):
      arm64: signal: Preserve POR_EL0 if poe_context is missing

Leo Yan (1):
      kselftest/arm64: Include <asm/ptrace.h> for user_gcs definition

Wentao Guan (1):
      arm64/scs: Fix potential sign extension issue of advance_loc4

Zhaoyang Huang (1):
      arm64: Reserve an extra page for early kernel mapping

 arch/arm64/include/asm/irqflags.h            | 14 ++++----
 arch/arm64/include/asm/kernel-pgtable.h      |  7 +++-
 arch/arm64/kernel/pi/patch-scs.c             |  4 +--
 arch/arm64/kernel/signal.c                   | 54 ++++++++++++++++++++++------
 drivers/acpi/arm64/cpuidle.c                 | 10 ++----
 tools/testing/selftests/arm64/gcs/gcs-util.h |  6 ----
 tools/testing/selftests/arm64/gcs/libc-gcs.c |  1 +
 7 files changed, 62 insertions(+), 34 deletions(-)

-- 
Catalin


             reply	other threads:[~2026-05-01 21:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-01 21:15 Catalin Marinas [this message]
2026-05-01 23:35 ` [GIT PULL] arm64 fixes for 7.1-rc2 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=afUX2gRwmgEfU0X1@arm.com \
    --to=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=will@kernel.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.