From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Sasha Levin <sashal@kernel.org>, stable <stable@vger.kernel.org>
Subject: Re: patches sent up to 6.13-rc1 that shouldn't be backported
Date: Tue, 1 Oct 2024 13:58:03 +0200 [thread overview]
Message-ID: <ZvvjyyO00fL_JL4q@zx2c4.com> (raw)
In-Reply-To: <2024100107-womb-share-931a@gregkh>
On Tue, Oct 01, 2024 at 08:52:28AM +0200, Greg Kroah-Hartman wrote:
> On Tue, Oct 01, 2024 at 06:02:45AM +0200, Jason A. Donenfeld wrote:
> > Hi Sasha,
> >
> > I've been getting emails from your bots...
> >
> > I sent two pulls to Linus for 6.13-rc1:
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4a39ac5b7d62679c07a3e3d12b0f6982377d8a7d
> > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=34e1a5d43c5deec563b94f3330b690dde9d1de53
> >
> > In these, I'm not sure there's actually much valid stable material. I
> > didn't mark anything as Cc: stable@vger.kernel.org, I don't think.
> >
> > As such, can you make sure none of those get backported?
> >
> > Alternatively, if you do have reason to want to pick some of these,
> > can you be clear with what and why, and actually carefully decide
> > which ones and which dependencies are required as such in a
> > non-automated way?
>
> They say so directly in the commit, i.e.:
> Stable-dep-of: 6eda706a535c ("selftests: vDSO: fix the way vDSO functions are called for powerpc")
Wha? Sasha added that. It's not in the original commit.
Is that tag anywhere in Linus' tree?
>
> in each one. So this seem to be needed to fix up the powerpc stuff.
>
> I'll drop them all if you feel these should not be applied.
Yes, thanks.
Jason
next prev parent reply other threads:[~2024-10-01 11:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-01 4:02 patches sent up to 6.13-rc1 that shouldn't be backported Jason A. Donenfeld
2024-10-01 6:52 ` Greg Kroah-Hartman
2024-10-01 11:58 ` Jason A. Donenfeld [this message]
2024-10-01 12:13 ` Greg Kroah-Hartman
2024-10-01 15:01 ` Jason A. Donenfeld
2024-10-02 7:31 ` Greg Kroah-Hartman
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=ZvvjyyO00fL_JL4q@zx2c4.com \
--to=jason@zx2c4.com \
--cc=gregkh@linuxfoundation.org \
--cc=sashal@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