public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	Vlastimil Babka <vbabka@suse.cz>,
	Oleksandr Natalenko <oleksandr@natalenko.name>,
	Jiri Benc <jbenc@redhat.com>,
	stable@vger.kernel.org,
	Thorsten Leemhuis <regressions@leemhuis.info>
Subject: Re: fs/bcachefs/
Date: Thu, 22 Feb 2024 06:54:10 -0500	[thread overview]
Message-ID: <Zdc14lqx0Yo_sYLe@sashalap> (raw)
In-Reply-To: <kcu4dlcablzlybppobcql7roqehim6ejkgsqkbw2rkrfv7xuch@edklzskv4iaa>

On Thu, Feb 22, 2024 at 01:30:01AM -0500, Kent Overstreet wrote:
>On Thu, Feb 22, 2024 at 06:48:58AM +0100, Greg KH wrote:
>> We NEED and REQUIRE you, if you do modify a commit from what is in
>> Linus's tree, to say "hey, this is modified because of X and Y", not to
>> just not say anything and assume that we should blindly take a modified
>> change.  You don't want us to do that, right?
>
>I can provide commit messages in the format you need - but also: _none_
>of this is documented in stable-kernel-rules.rst, so I'm going to want
>something clear and specific I can go off of.

This part is explicitly documented in stable-kernel-rules.rst. In
particular, it lists the 3 ways one could send us commits for inclusion
(https://docs.kernel.org/process/stable-kernel-rules.html#procedure-for-submitting-patches-to-the-stable-tree).
To summarize, it's your choice of:

1. Tag it with a stable@ tag. OR:
2. Send us a mail to the stable mailing list with commit IDs for us to
cherry pick. OR:
3. Send the patches themselves (which is the option you've picked), and
then the doc proceeds to call out how to include the upstream commit ID
in the patch
(https://docs.kernel.org/process/stable-kernel-rules.html#option-3).

-- 
Thanks,
Sasha

  reply	other threads:[~2024-02-22 11:54 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-15 22:12 fs/bcachefs/ Kent Overstreet
2024-01-15 23:03 ` fs/bcachefs/ Sasha Levin
2024-02-20 17:23   ` fs/bcachefs/ Kent Overstreet
2024-02-20 18:03     ` fs/bcachefs/ Greg KH
2024-02-20 18:53       ` fs/bcachefs/ Greg KH
2024-02-20 20:06         ` fs/bcachefs/ Kent Overstreet
2024-02-20 20:19           ` fs/bcachefs/ Greg KH
2024-02-20 20:22             ` fs/bcachefs/ Kent Overstreet
2024-02-20 20:39               ` fs/bcachefs/ Greg KH
2024-02-20 20:42                 ` fs/bcachefs/ Kent Overstreet
2024-02-20 20:39             ` fs/bcachefs/ Kent Overstreet
2024-02-20 20:51               ` fs/bcachefs/ Greg KH
2024-02-20 21:00                 ` fs/bcachefs/ Kent Overstreet
2024-02-21 14:53                   ` fs/bcachefs/ Greg KH
2024-02-21 16:00                     ` fs/bcachefs/ Oleksandr Natalenko
2024-02-21 17:57                       ` fs/bcachefs/ Greg KH
2024-02-21 18:10                         ` fs/bcachefs/ Vlastimil Babka
2024-02-21 20:52                           ` fs/bcachefs/ Kent Overstreet
2024-02-21 22:58                           ` fs/bcachefs/ Sasha Levin
2024-02-21 23:12                             ` fs/bcachefs/ Kent Overstreet
2024-02-22  5:48                               ` fs/bcachefs/ Greg KH
2024-02-22  6:30                                 ` fs/bcachefs/ Kent Overstreet
2024-02-22 11:54                                   ` Sasha Levin [this message]
2024-02-21 23:47                             ` fs/bcachefs/ Oleksandr Natalenko
2024-02-22 19:19                           ` stable-kernel-rules was fs/bcachefs/ Pavel Machek
2024-02-22 22:33                             ` Kent Overstreet
2024-02-23 18:50                               ` Pavel Machek
2024-02-20 19:36     ` fs/bcachefs/ Sasha Levin
2024-01-16 14:13 ` fs/bcachefs/ Greg KH
2024-01-16 17:26   ` fs/bcachefs/ Kent Overstreet
2024-01-16 17:44     ` fs/bcachefs/ 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=Zdc14lqx0Yo_sYLe@sashalap \
    --to=sashal@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jbenc@redhat.com \
    --cc=kent.overstreet@linux.dev \
    --cc=oleksandr@natalenko.name \
    --cc=regressions@leemhuis.info \
    --cc=stable@vger.kernel.org \
    --cc=vbabka@suse.cz \
    /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