From: Mark Rutland <mark.rutland@arm.com>
To: Rahul Sharma <black.hawk@163.com>
Cc: gregkh@linuxfoundation.org, stable@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6.12.y 0/2] Fix patch backport review
Date: Tue, 3 Mar 2026 13:08:13 +0000 [thread overview]
Message-ID: <aabdPVl_2PSvbn0p@J2N7QTR9R3.cambridge.arm.com> (raw)
In-Reply-To: <20260303015047.2014999-1-black.hawk@163.com>
On Tue, Mar 03, 2026 at 09:50:45AM +0800, Rahul Sharma wrote:
> This patch series is to backport the fix d2907cbe9ea0
> ("arm64/fpsimd: signal: Fix restoration of SVE context")
> to 6.12.y and the first patch
> ("arm64/fpsimd: signal: Mandate SVE payload for streaming-mode state")
> is its dependence.
Neither of these need to be backported to the v6.12.y stable tree.
In the v6.12.y stable tree CONFIG_ARM64_SME depends on BROKEN, and these
patches only matter when CONFIG_ARM64_SME=y. I think we should leave
that BROKEN in the v6.12.y stable tree given that suddenly enabling SME
for distros could cause all sorts of surprises.
If you are going to backport patches I have written, please CC me on
those backports.
Mark.
> Mark Rutland (2):
> arm64/fpsimd: signal: Mandate SVE payload for streaming-mode state
> arm64/fpsimd: signal: Fix restoration of SVE context
>
> arch/arm64/kernel/signal.c | 36 ++++++++++++++++++++++++++++--------
> 1 file changed, 28 insertions(+), 8 deletions(-)
>
> --
> 2.34.1
>
prev parent reply other threads:[~2026-03-03 13:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-03 1:50 Rahul Sharma
2026-03-03 1:50 ` [PATCH 6.12.y 1/2] arm64/fpsimd: signal: Mandate SVE payload for streaming-mode state Rahul Sharma
2026-03-03 1:50 ` [PATCH 6.12.y 2/2] arm64/fpsimd: signal: Fix restoration of SVE context Rahul Sharma
2026-03-03 13:08 ` Mark Rutland [this message]
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=aabdPVl_2PSvbn0p@J2N7QTR9R3.cambridge.arm.com \
--to=mark.rutland@arm.com \
--cc=black.hawk@163.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.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
all inboxes | Powered by JetHome®