From: Catalin Marinas <cmarinas@kernel.org>
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 6.15-rc1
Date: Thu, 3 Apr 2025 11:03:22 +0100 [thread overview]
Message-ID: <Z-5c6hCqQb3s5GxI@arm.com> (raw)
Hi Linus,
Please pull the arm64 fixes below that turned up during or shortly
before the merging window. They are based on top of the previous arm64
updates pull request (6.14-rc3).
(sending with my kernel.org address, hopefully not ending in spam this
time around)
Thanks.
The following changes since commit 64fa6b9322a904198589c0479dca6f2ed7f2eb04:
Merge branch 'for-next/el2-enable-feat-pmuv3p9' into for-next/core (2025-03-25 19:32:32 +0000)
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 c28f31deeacda307acfee2f18c0ad904e5123aac:
arm64: Don't call NULL in do_compat_alignment_fixup() (2025-04-01 14:13:11 +0100)
----------------------------------------------------------------
arm64 fixes:
- Fix max_pfn calculation when hotplugging memory so that it never
decreases
- Fix dereference of unused source register in the MOPS SET operation
fault handling
- Fix NULL calling in do_compat_alignment_fixup() when the 32-bit user
space does an unaligned LDREX/STREX
- Add the HiSilicon HIP09 processor to the Spectre-BHB affected CPUs
- Drop unused code pud accessors (special/mkspecial)
----------------------------------------------------------------
Angelos Oikonomopoulos (1):
arm64: Don't call NULL in do_compat_alignment_fixup()
Jinqian Yang (1):
arm64: Add support for HIP09 Spectre-BHB mitigation
Keir Fraser (1):
arm64: mops: Do not dereference src reg for a set operation
Peter Xu (1):
arm64: mm: Drop dead code for pud special bit handling
Zhenhua Huang (1):
arm64: mm: Correct the update of max_pfn
arch/arm64/include/asm/cputype.h | 2 ++
arch/arm64/include/asm/pgtable.h | 5 -----
arch/arm64/include/asm/traps.h | 4 ++--
arch/arm64/kernel/compat_alignment.c | 2 ++
arch/arm64/kernel/proton-pack.c | 1 +
arch/arm64/mm/mmu.c | 3 ++-
6 files changed, 9 insertions(+), 8 deletions(-)
--
Catalin
next reply other threads:[~2025-04-03 10:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-03 10:03 Catalin Marinas [this message]
2025-04-03 19:33 ` [GIT PULL] arm64 fixes for 6.15-rc1 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=Z-5c6hCqQb3s5GxI@arm.com \
--to=cmarinas@kernel.org \
--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 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).