public inbox for linux-bcache@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Michael Lyle <mlyle@lyle.org>,
	linux-bcache@vger.kernel.org, linux-block@vger.kernel.org
Subject: Re: [416 PATCH 00/13] Bcache changes for 4.16
Date: Mon, 8 Jan 2018 13:42:41 -0700	[thread overview]
Message-ID: <0692a21d-8465-9c1e-93a5-cf96dfb36cda@kernel.dk> (raw)
In-Reply-To: <20180108202130.31303-1-mlyle@lyle.org>

On 1/8/18 1:21 PM, Michael Lyle wrote:
> Jens,
> 
> Please pick up the following reviewed changes for 4.16.  There's some
> small cleanliness changes, a few minor bug fixes (some in preparation
> for larger work), and ongoing work on writeback performance:
> 
>  11 files changed, 303 insertions(+), 133 deletions(-)
> 
> Coly Li (2):
>       bcache: reduce cache_set devices iteration by devices_max_used
>       bcache: fix misleading error message in bch_count_io_errors()
> 
> Kent Overstreet (2):
>       bcache: Fix, improve efficiency of closure_sync()
>       bcache: mark closure_sync() __sched
> 
> Michael Lyle (3):
>       bcache: writeback: properly order backing device IO
>       bcache: allow quick writeback when backing idle
>       bcache: fix writeback target calc on large devices
> 
> Rui Hua (1):
>       bcache: ret IOERR when read meets metadata error
> 
> Tang Junhui (3):
>       bcache: stop writeback thread after detaching
>       bcache: segregate flash only volume write streams
>       bcache: fix wrong return value in bch_debug_init()
> 
> Vasyl Gomonovych (1):
>       bcache: Use PTR_ERR_OR_ZERO()
> 
> Zhai Zhaoxuan (1):
>       bcache: fix unmatched generic_end_io_acct() & generic_start_io_acct()

Looks good, thanks Mike. Applied for 4.16.

-- 
Jens Axboe

      parent reply	other threads:[~2018-01-08 20:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-08 20:21 [416 PATCH 00/13] Bcache changes for 4.16 Michael Lyle
2018-01-08 20:21 ` [416 PATCH 01/13] bcache: ret IOERR when read meets metadata error Michael Lyle
2018-01-08 20:21 ` [416 PATCH 02/13] bcache: stop writeback thread after detaching Michael Lyle
2018-01-08 20:21 ` [416 PATCH 03/13] bcache: Use PTR_ERR_OR_ZERO() Michael Lyle
2018-01-08 20:21 ` [416 PATCH 04/13] bcache: segregate flash only volume write streams Michael Lyle
2018-01-08 20:21 ` [416 PATCH 05/13] bcache: fix wrong return value in bch_debug_init() Michael Lyle
2018-01-08 20:21 ` [416 PATCH 06/13] bcache: writeback: properly order backing device IO Michael Lyle
2018-01-08 20:21 ` [416 PATCH 07/13] bcache: allow quick writeback when backing idle Michael Lyle
2018-01-08 20:21 ` [416 PATCH 08/13] bcache: Fix, improve efficiency of closure_sync() Michael Lyle
2018-01-08 20:21 ` [416 PATCH 09/13] bcache: mark closure_sync() __sched Michael Lyle
2018-01-08 20:21 ` [416 PATCH 10/13] bcache: fix unmatched generic_end_io_acct() & generic_start_io_acct() Michael Lyle
2018-01-08 20:21 ` [416 PATCH 11/13] bcache: reduce cache_set devices iteration by devices_max_used Michael Lyle
2018-01-08 20:21 ` [416 PATCH 12/13] bcache: fix misleading error message in bch_count_io_errors() Michael Lyle
2018-01-08 20:21 ` [416 PATCH 13/13] bcache: fix writeback target calc on large devices Michael Lyle
2018-01-08 20:42 ` Jens Axboe [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=0692a21d-8465-9c1e-93a5-cf96dfb36cda@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=linux-bcache@vger.kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=mlyle@lyle.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