From: Heiko Carstens <hca@linux.ibm.com>
To: stable@vger.kernel.org
Cc: stable-commits@vger.kernel.org, Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Sven Schnelle <svens@linux.ibm.com>
Subject: Re: Patch "s390/entry: Fix last breaking event handling in case of stack corruption" has been added to the 6.6-stable tree
Date: Mon, 12 May 2025 10:02:44 +0200 [thread overview]
Message-ID: <20250512080244.12203Abb-hca@linux.ibm.com> (raw)
In-Reply-To: <20250511175902.3461288-1-sashal@kernel.org>
On Sun, May 11, 2025 at 01:59:02PM -0400, Sasha Levin wrote:
> This is a note to let you know that I've just added the patch titled
>
> s390/entry: Fix last breaking event handling in case of stack corruption
>
> to the 6.6-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:
> s390-entry-fix-last-breaking-event-handling-in-case-.patch
> and it can be found in the queue-6.6 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.
This patch shouldn't be applied as it is to 6.6, 6.1, and 5.15 stable kernels,
since it won't compile. I'll provide a slightly modified variant.
next parent reply other threads:[~2025-05-12 8:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250511175902.3461288-1-sashal@kernel.org>
2025-05-12 8:02 ` Heiko Carstens [this message]
2025-05-12 9:13 ` Patch "s390/entry: Fix last breaking event handling in case of stack corruption" has been added to the 6.6-stable tree Greg KH
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=20250512080244.12203Abb-hca@linux.ibm.com \
--to=hca@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=svens@linux.ibm.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