From: Greg KH <gregkh@linuxfoundation.org>
To: Oleksandr Natalenko <oleksandr@natalenko.name>
Cc: Kent Overstreet <kent.overstreet@linux.dev>,
Jiri Benc <jbenc@redhat.com>, Sasha Levin <sashal@kernel.org>,
stable@vger.kernel.org, Vlastimil Babka <vbabka@suse.cz>,
Thorsten Leemhuis <regressions@leemhuis.info>
Subject: Re: fs/bcachefs/
Date: Wed, 21 Feb 2024 18:57:54 +0100 [thread overview]
Message-ID: <2024022155-reformat-scorer-98ae@gregkh> (raw)
In-Reply-To: <4900587.31r3eYUQgx@natalenko.name>
On Wed, Feb 21, 2024 at 05:00:05PM +0100, Oleksandr Natalenko wrote:
> On středa 21. února 2024 15:53:11 CET Greg KH wrote:
> > Given the huge patch volume that the stable tree manages (30-40 changes
> > accepted a day, 7 days a week), any one kernel subsystem that wishes to
> > do something different only slows down everyone else.
>
> Lower down the volume then? Raise the bar for what gets backported?
> Stable kernel releases got unnecessarily big [1] (Jiří is in Cc).
> Those 40 changes a day cannot get a proper review. Each stable release
> tries to mimic -rc except -rc is in consistent state while "stable" is
> just a bunch of changes picked here and there.
If you can point out any specific commits that we should not be taking,
please let us know.
Personally I think we are not taking enough, and are still missing real
fixes. Overall, this is only a very small % of what goes into Linus's
tree every day, so by that measure alone, we know we are missing things.
thanks,
greg k-h
next prev parent reply other threads:[~2024-02-21 17:57 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 ` Greg KH [this message]
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=2024022155-reformat-scorer-98ae@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=jbenc@redhat.com \
--cc=kent.overstreet@linux.dev \
--cc=oleksandr@natalenko.name \
--cc=regressions@leemhuis.info \
--cc=sashal@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.