public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
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 17:01:12 +0200	[thread overview]
Message-ID: <ZvwOuERpwrkG5KPN@zx2c4.com> (raw)
In-Reply-To: <2024100120-unlucky-sample-091b@gregkh>

On Tue, Oct 01, 2024 at 02:13:14PM +0200, Greg Kroah-Hartman wrote:
> Ok, I'll try to rework the other dependant patches to see if we can get
> that fix in somehow without this change.  But why not take this, what is
> it hurting?

I just don't see the need to backport *any* patches from my tree that
don't have an explicit Cc: stable@ marker on them. I'm pretty careful
about adding those, and when I forget, I send them manually onward to
stable@. If there's some judgement that a certain patch needs to be
backported that I didn't mark, that sounds like something to
deliberately raise, rather than a heap of emails that this patch and
that patch have been added willy-nilly.

The reason I care about this is that I generally care about stable and
consistency of rationale and such, and so if you *do* want to backport
some stuff, I am going to spend time checking and verifying and being
careful. I don't want to do that work if it's just the consequence of a
random script and not somebody's technical decision.

  reply	other threads:[~2024-10-01 15:01 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
2024-10-01 12:13     ` Greg Kroah-Hartman
2024-10-01 15:01       ` Jason A. Donenfeld [this message]
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=ZvwOuERpwrkG5KPN@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