* [CHERRY-PICK] bcache: fixes that missed a Cc: stable@vger.kernel.org
@ 2023-03-03 21:26 Eric Wheeler
2023-03-04 6:46 ` Greg KH
0 siblings, 1 reply; 3+ messages in thread
From: Eric Wheeler @ 2023-03-03 21:26 UTC (permalink / raw)
To: stable; +Cc: linux-bcache, Coly Li
Dear stable tree maintainers:
Please pick the following commits that should be pulled into stable but
missed the `Cc` tag to make it happen automatically.
I have checked with Coly, the bcache maintainer, and he agrees that they
should go into stable:
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()
# NOTICE: 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
Thanks!
--
Eric Wheeler
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [CHERRY-PICK] bcache: fixes that missed a Cc: stable@vger.kernel.org
2023-03-03 21:26 [CHERRY-PICK] bcache: fixes that missed a Cc: stable@vger.kernel.org Eric Wheeler
@ 2023-03-04 6:46 ` Greg KH
2023-03-15 8:05 ` Greg KH
0 siblings, 1 reply; 3+ messages in thread
From: Greg KH @ 2023-03-04 6:46 UTC (permalink / raw)
To: Eric Wheeler; +Cc: stable, linux-bcache, Coly Li
On Fri, Mar 03, 2023 at 01:26:53PM -0800, Eric Wheeler wrote:
> Dear stable tree maintainers:
>
> Please pick the following commits that should be pulled into stable but
> missed the `Cc` tag to make it happen automatically.
>
> I have checked with Coly, the bcache maintainer, and he agrees that they
> should go into stable:
>
>
> 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()
>
> # NOTICE: 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
What stable tree(s) should these all go to?
thanks,
greg k-h
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [CHERRY-PICK] bcache: fixes that missed a Cc: stable@vger.kernel.org
2023-03-04 6:46 ` Greg KH
@ 2023-03-15 8:05 ` Greg KH
0 siblings, 0 replies; 3+ messages in thread
From: Greg KH @ 2023-03-15 8:05 UTC (permalink / raw)
To: Eric Wheeler; +Cc: stable, linux-bcache, Coly Li
On Sat, Mar 04, 2023 at 07:46:07AM +0100, Greg KH wrote:
> On Fri, Mar 03, 2023 at 01:26:53PM -0800, Eric Wheeler wrote:
> > Dear stable tree maintainers:
> >
> > Please pick the following commits that should be pulled into stable but
> > missed the `Cc` tag to make it happen automatically.
> >
> > I have checked with Coly, the bcache maintainer, and he agrees that they
> > should go into stable:
> >
> >
> > 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()
> >
> > # NOTICE: 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
>
> What stable tree(s) should these all go to?
Dropped from my queue due to lack of response :(
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2023-03-15 8:06 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-03-03 21:26 [CHERRY-PICK] bcache: fixes that missed a Cc: stable@vger.kernel.org Eric Wheeler
2023-03-04 6:46 ` Greg KH
2023-03-15 8:05 ` Greg KH
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox