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 -rc5
Date: Fri, 16 Feb 2024 11:58:20 +0000 [thread overview]
Message-ID: <20240216115819.GA1804@willie-the-truck> (raw)
Hi Linus,
Please pull these arm64 fixes for -rc5. It's a little busier than normal,
but it's still not a lot of code and things seem fairly quiet in general.
Summary in the tag.
Cheers,
Will
--->8
The following changes since commit 54be6c6c5ae8e0d93a6c4641cb7528eb0b6ba478:
Linux 6.8-rc3 (2024-02-04 12:20:36 +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 2813926261e436d33bc74486b51cce60b76edf78:
arm64/sve: Lower the maximum allocation for the SVE ptrace regset (2024-02-15 11:48:00 +0000)
----------------------------------------------------------------
arm64 fixes for -rc5
- Fix allocation failure during SVE coredumps
- Fix handling of SVE context on signal delivery
- Enable Neoverse N2 CPU errata workarounds for Microsoft's
"Azure Cobalt 100" clone
- Work around CMN PMU erratum in AmpereOneX implementation
- Fix typo in CXL PMU event definition
- Fix jump label asm constraints
----------------------------------------------------------------
Easwar Hariharan (1):
arm64: Subscribe Microsoft Azure Cobalt 100 to ARM Neoverse N2 errata
Fangrui Song (1):
arm64: jump_label: use constraints "Si" instead of "i"
Hojin Nam (1):
perf: CXL: fix mismatched cpmu event opcode
Ilkka Koskinen (1):
perf/arm-cmn: Workaround AmpereOneX errata AC04_MESH_1 (incorrect child count)
Mark Brown (2):
arm64/signal: Don't assume that TIF_SVE means we saved SVE state
arm64/sve: Lower the maximum allocation for the SVE ptrace regset
Seongsu Park (1):
arm64: fix typo in comments
Documentation/arch/arm64/silicon-errata.rst | 7 +++++++
arch/arm64/include/asm/cpufeature.h | 2 +-
arch/arm64/include/asm/cputype.h | 4 ++++
arch/arm64/include/asm/fpsimd.h | 12 ++++++------
arch/arm64/include/asm/jump_label.h | 12 ++++++++----
arch/arm64/kernel/cpu_errata.c | 3 +++
arch/arm64/kernel/fpsimd.c | 2 +-
arch/arm64/kernel/ptrace.c | 3 ++-
arch/arm64/kernel/signal.c | 4 ++--
drivers/perf/arm-cmn.c | 11 +++++++++++
drivers/perf/cxl_pmu.c | 2 +-
11 files changed, 46 insertions(+), 16 deletions(-)
next reply other threads:[~2024-02-16 11:58 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-16 11:58 Will Deacon [this message]
2024-02-16 18:52 ` [GIT PULL] arm64 fixes for -rc5 pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2023-10-06 7:56 Will Deacon
2023-10-06 15:15 ` pr-tracker-bot
2023-07-21 11:44 Will Deacon
2023-07-21 11:45 ` Will Deacon
2023-07-21 17:28 ` pr-tracker-bot
2022-09-11 11:37 Will Deacon
2022-09-11 19:36 ` pr-tracker-bot
2021-08-06 13:53 Will Deacon
2021-08-06 18:40 ` Linus Torvalds
2021-08-09 10:52 ` Will Deacon
2021-08-06 18:48 ` pr-tracker-bot
2021-03-25 14:54 [GIT PULL] arm64: Fixes " Will Deacon
2021-03-25 19:13 ` pr-tracker-bot
2020-07-10 14:39 [GIT PULL] arm64 fixes " Will Deacon
2020-07-10 16:55 ` pr-tracker-bot
2020-03-06 15:12 Will Deacon
2020-03-06 20:55 ` pr-tracker-bot
2019-06-14 15:02 [GIT PULL] arm64: " Will Deacon
2019-06-14 16:20 ` pr-tracker-bot
2019-04-12 16:05 [GIT PULL] arm64 " Will Deacon
2019-04-13 17:40 ` pr-tracker-bot
2019-02-01 17:51 [GIT PULL] arm64: " Will Deacon
2019-02-02 1:00 ` pr-tracker-bot
2018-05-11 17:30 Will Deacon
2017-03-31 17:15 Will Deacon
2016-06-24 11:41 Will Deacon
2016-02-19 16:29 Will Deacon
2015-10-07 14:20 Will Deacon
2015-01-16 17:16 Will Deacon
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=20240216115819.GA1804@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;
as well as URLs for NNTP newsgroup(s).