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 6.1-rc4
Date: Fri, 4 Nov 2022 23:12:45 +0000 [thread overview]
Message-ID: <Y2WcbQM5P2aJrf7o@arm.com> (raw)
Hi Linus,
Please pull the arm64 fixes below. Thanks.
The following changes since commit 9abf2313adc1ca1b6180c508c25f22f9395cc780:
Linux 6.1-rc1 (2022-10-16 15:36:24 -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 85f1506337f0c79a4955edfeee86a18628e3735f:
arm64: cpufeature: Fix the visibility of compat hwcaps (2022-11-03 18:04:56 +0000)
----------------------------------------------------------------
arm64 fixes:
- Avoid kprobe recursion when cortex_a76_erratum_1463225_debug_handler()
is not inlined (change to __always_inline).
- Fix the visibility of compat hwcaps, broken by recent changes to
consolidate the visibility of hwcaps and the user-space view of the ID
registers.
----------------------------------------------------------------
Amit Daniel Kachhap (1):
arm64: cpufeature: Fix the visibility of compat hwcaps
Mark Rutland (1):
arm64: entry: avoid kprobe recursion
Documentation/arm64/cpu-feature-registers.rst | 38 +++++++++++++++++++++++-
arch/arm64/kernel/cpufeature.c | 42 +++++++++++++++++++++------
arch/arm64/kernel/entry-common.c | 3 +-
3 files changed, 72 insertions(+), 11 deletions(-)
--
Catalin
next reply other threads:[~2022-11-04 23:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-04 23:12 Catalin Marinas [this message]
2022-11-05 2:54 ` [GIT PULL] arm64 fixes for 6.1-rc4 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=Y2WcbQM5P2aJrf7o@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox