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.5-rc5
Date: Fri, 4 Aug 2023 19:56:31 +0100 [thread overview]
Message-ID: <ZM1J35gT1jjr96Vh@arm.com> (raw)
Hi Linus,
Please pull the arm64 fixes below. Thanks.
The following changes since commit 003e6b56d780095a9adc23efc9cb4b4b4717169b:
ACPI/IORT: Remove erroneous id_count check in iort_node_get_rmr_info() (2023-07-28 14:50:50 +0100)
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 69af56ae56a48a2522aad906c4461c6c7c092737:
arm64/fpsimd: Sync and zero pad FPSIMD state for streaming SVE (2023-08-04 16:18:32 +0100)
----------------------------------------------------------------
More SVE/SME fixes for ptrace() and for the (potentially future) case
where SME is implemented in hardware without SVE support.
----------------------------------------------------------------
Mark Brown (5):
arm64/fpsimd: Clear SME state in the target task when setting the VL
arm64/ptrace: Flush FP state when setting ZT0
arm64/ptrace: Don't enable SVE when setting streaming SVE
arm64/fpsimd: Sync FPSIMD state with SVE for SME only systems
arm64/fpsimd: Sync and zero pad FPSIMD state for streaming SVE
arch/arm64/kernel/fpsimd.c | 9 +++++----
arch/arm64/kernel/ptrace.c | 10 +++++++---
2 files changed, 12 insertions(+), 7 deletions(-)
--
Catalin
next reply other threads:[~2023-08-04 18:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-04 18:56 Catalin Marinas [this message]
2023-08-04 19:15 ` [GIT PULL] arm64 fixes for 6.5-rc5 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=ZM1J35gT1jjr96Vh@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