From: Sasha Levin <sashal@kernel.org>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: stable@vger.kernel.org
Subject: Re: fs/bcachefs/
Date: Mon, 15 Jan 2024 18:03:11 -0500 [thread overview]
Message-ID: <ZaW5r5kRbOcKveVn@sashalap> (raw)
In-Reply-To: <g6el7eghhdk2v5osukhobvi4pige5bsfu5koqtmoyeknat36t7@irmmk7zo7edh>
On Mon, Jan 15, 2024 at 05:12:17PM -0500, Kent Overstreet wrote:
>Hi stable team - please don't take patches for fs/bcachefs/ except from
>myself; I'll be doing backports and sending pull requests after stuff
>has been tested by my CI.
>
>Thanks, and let me know if there's any other workflow things I should
>know about
Sure, we can ignore fs/bcachefs/ patches.
Note that the proposed workflow would only work through patches coming
through your tree, but patches in other subsystems that could affect
bcachefs might break it in stable trees without being caught by your CI.
I'd recommend integrating your pre-release tests with something like
kernelci, which would let us catch bcachefs-affecting issues coming from
other sources.
What more, if we do the above, we could in the future avoid special
casing bcachefs :)
--
Thanks,
Sasha
next prev parent reply other threads:[~2024-01-15 23:03 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 ` Sasha Levin [this message]
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 ` fs/bcachefs/ Sasha Levin
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=ZaW5r5kRbOcKveVn@sashalap \
--to=sashal@kernel.org \
--cc=kent.overstreet@linux.dev \
--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