From: Coly Li <colyli@suse.de>
To: Eric Wheeler <bcache@lists.ewheeler.net>
Cc: linux-bcache@vger.kernel.org
Subject: Re: bugfix commits since 5.15 not marked with Cc: stable
Date: Tue, 28 Feb 2023 11:57:40 +0800 [thread overview]
Message-ID: <5B7D9629-C505-4668-9989-0F998BD0A8CA@suse.de> (raw)
In-Reply-To: <577d7e59-33ff-77bb-5a31-a18d7ca9834a@ewheeler.net>
> 2023年2月28日 08:56，Eric Wheeler <bcache@lists.ewheeler.net> 写道：
>
> Hello Coly,
Hi Eric,
>
> I was looking through the commits between 5.15 and the latest kernel
> release. It looks like the following commits may benefit from being marked
> for inclusion in the stable kernel trees.
>
> Is there any reason that any of these should be excluded from the stable
> release kernels?
>
> d55f7cb2e5c0 bcache: fix error info in register_bcache()
> 7b1002f7cfe5 bcache: fixup bcache_dev_sectors_dirty_add() multithreaded CPU false sharing
> a1a2d8f0162b bcache: avoid unnecessary soft lockup in kworker update_writeback_rate()
>
> # These two depend on each other, so apply both or neither:
> 0259d4498ba4 bcache: move calc_cached_dev_sectors to proper place on backing device detach
> aa97f6cdb7e9 bcache: fix NULL pointer reference in cached_dev_detach_finish
>
> If they look good to you then I will write an email to the stable list.
It was just because the original patches didn’t do that. And yes I do appreciate to send them to stable maintainer.
Thank you for the help :-)
Coly Li
prev parent reply other threads:[~2023-02-28 3:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 0:56 bugfix commits since 5.15 not marked with Cc: stable Eric Wheeler
2023-02-28 3:57 ` Coly Li [this message]
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=5B7D9629-C505-4668-9989-0F998BD0A8CA@suse.de \
--to=colyli@suse.de \
--cc=bcache@lists.ewheeler.net \
--cc=linux-bcache@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).