Linux bcache driver list
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Eric Wheeler <stable@lists.ewheeler.net>
Cc: stable@vger.kernel.org, linux-bcache@vger.kernel.org,
	Coly Li <colyli@suse.de>
Subject: Re: [CHERRY-PICK] bcache: fixes that missed a Cc: stable@vger.kernel.org
Date: Sat, 4 Mar 2023 07:46:07 +0100	[thread overview]
Message-ID: <ZALpL/xVJHFwuCIL@kroah.com> (raw)
In-Reply-To: <81201ca-5263-1b20-8e21-8c88edb552c9@ewheeler.net>

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

  reply	other threads:[~2023-03-04  6:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2023-03-15  8:05   ` 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=ZALpL/xVJHFwuCIL@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=colyli@suse.de \
    --cc=linux-bcache@vger.kernel.org \
    --cc=stable@lists.ewheeler.net \
    --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