From: Marc Zyngier <maz@kernel.org>
To: stable@vger.kernel.org
Cc: stable-commits@vger.kernel.org, oupton@kernel.org,
Joey Gouly <joey.gouly@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>
Subject: Re: Patch "KVM: arm64: Advertise support for FEAT_SCTLR2" has been added to the 6.12-stable tree
Date: Sat, 07 Mar 2026 16:44:31 +0000 [thread overview]
Message-ID: <87zf4jd1xs.wl-maz@kernel.org> (raw)
In-Reply-To: <20260307131250.3919487-1-sashal@kernel.org>
On Sat, 07 Mar 2026 13:12:50 +0000,
Sasha Levin <sashal@kernel.org> wrote:
>
> This is a note to let you know that I've just added the patch titled
>
> KVM: arm64: Advertise support for FEAT_SCTLR2
>
> to the 6.12-stable tree which can be found at:
> http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
>
> The filename of the patch is:
> kvm-arm64-advertise-support-for-feat_sctlr2.patch
> and it can be found in the queue-6.12 subdirectory.
>
> If you, or anyone else, feels it should not be added to the stable tree,
> please let <stable@vger.kernel.org> know about it.
Of course it should not. And the reason is written in the commit log:
> Everything is in place to handle the additional state for SCTLR2_ELx,
> which is all that FEAT_SCTLR2 implies.
Where is that handling? Oh wait, it's not there. That's only 20
patches you're missing.
Now you are advertising a new feature to guests, which is not context
switched, and offering potential control from guests on the host. But
hey, who cares about that...
If you cannot be bothered to resolve trivial conflicts, please don't.
Fail the backport, and someone who actually cares will do the work.
M.
--
Jazz isn't dead. It just smells funny.
parent reply other threads:[~2026-03-07 16:44 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20260307131250.3919487-1-sashal@kernel.org>]
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=87zf4jd1xs.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=joey.gouly@arm.com \
--cc=oupton@kernel.org \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=suzuki.poulose@arm.com \
--cc=will@kernel.org \
--cc=yuzenghui@huawei.com \
/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