From: Greg KH <gregkh@linuxfoundation.org>
To: Alyssa Ross <hi@alyssa.is>
Cc: Sasha Levin <sashal@kernel.org>,
stable@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Tom Rix <trix@redhat.com>
Subject: Re: Patch "purgatory: fix disabling debug info" has been added to the 5.15-stable tree
Date: Tue, 18 Apr 2023 13:19:39 +0200 [thread overview]
Message-ID: <2023041837-dial-catchable-0203@gregkh> (raw)
In-Reply-To: <20230418103951.2b7kia6nb2zdeqje@x220>
On Tue, Apr 18, 2023 at 10:39:51AM +0000, Alyssa Ross wrote:
> On Mon, Apr 17, 2023 at 09:27:22PM -0400, Sasha Levin wrote:
> > This is a note to let you know that I've just added the patch titled
> >
> > purgatory: fix disabling debug info
> >
> > to the 5.15-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:
> > purgatory-fix-disabling-debug-info.patch
> > and it can be found in the queue-5.15 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.
>
> There's no need for this patch on 5.15, as the regression it fixes was
> only introduced in 6.0.
Not according to the information in this commit, which says:
Fixes: 32ef9e5054ec ("Makefile.debug: re-enable debug info for .S files")
And that commit is in the following releases:
4.19.264 5.4.221 5.10.152 5.15.76 5.19.12 6.0
So it should be also in 5.4.y and 4.19.y, right?
thanks,
greg k-h
next prev parent reply other threads:[~2023-04-18 11:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230418012722.330253-1-sashal@kernel.org>
2023-04-18 10:39 ` Patch "purgatory: fix disabling debug info" has been added to the 5.15-stable tree Alyssa Ross
2023-04-18 11:18 ` Sasha Levin
2023-04-18 11:19 ` Greg KH [this message]
2023-04-18 15:42 ` Alyssa Ross
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=2023041837-dial-catchable-0203@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hi@alyssa.is \
--cc=hpa@zytor.com \
--cc=mingo@redhat.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=trix@redhat.com \
--cc=x86@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