linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Mike Snitzer <snitzer@redhat.com>
Cc: Kent Overstreet <kent.overstreet@gmail.com>,
	linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
	hch@infradead.org, colyli@suse.de, darrick.wong@oracle.com,
	clm@fb.com, bacik@fb.com, linux-xfs@vger.kernel.org,
	drbd-dev@lists.linbit.com, linux-btrfs@vger.kernel.org,
	linux-raid@vger.kernel.org, neilb@suse.com
Subject: Re: [PATCH 00/13] convert block layer to bioset_init()/mempool_init()
Date: Wed, 30 May 2018 13:38:49 -0600	[thread overview]
Message-ID: <5f32b2e7-859b-42f9-c726-115ba5ff22a9@kernel.dk> (raw)
In-Reply-To: <20180530193707.GB6568@redhat.com>

On 5/30/18 1:37 PM, Mike Snitzer wrote:
> On Wed, May 30 2018 at  2:55pm -0400,
> Jens Axboe <axboe@kernel.dk> wrote:
> 
>> On 5/30/18 7:36 AM, Mike Snitzer wrote:
>>> So revisiting this patchset: are you inclined to take these changes (I
>>> assume yes)?  If so, what would you need in order to get them staged for
>>> 4.18?  I'll start with offering my review in reply to the DM patch.  I'd
>>> much prefer to see this level of change go in sooner rather than later.
>>
>> Yeah I'd like to take the changes, but we might have to wait for
>> 4.19 at this point. It'd certainly help to have the dm bits reviewed,
>> as they are some of the larger ones. The grunt of the others are mostly
>> trivial and smaller in scope.
> 
> I _really_ would like to see this land for 4.18.  It'll avoid downstream
> backport problems (due to all the churn in this patchset).
> 
> As I'm sure you've seen I reviewed and Acked-by the DM patch.
> 
> I mentioned I've been chatting with Kent, he is available if anything
> needs a v2 for whatever reason.
> 
> Would you be OK adding a single sentence description to each driver's
> patch header (rather than leaving empty like how Kent submitted)?  Or
> should Kent resubmit the entire set with that boilerplate header for
> each patch?

See previous email for both questions :)

-- 
Jens Axboe


  reply	other threads:[~2018-05-30 19:38 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-20 22:25 [PATCH 00/13] convert block layer to bioset_init()/mempool_init() Kent Overstreet
2018-05-20 22:25 ` [PATCH 01/12] block: convert bounce, q->bio_split " Kent Overstreet
2018-05-22 10:08   ` Christoph Hellwig
2018-05-20 22:25 ` [PATCH 02/12] drbd: convert " Kent Overstreet
2018-05-20 22:25 ` [PATCH 03/12] pktcdvd: " Kent Overstreet
2018-05-20 22:25 ` [PATCH 04/12] lightnvm: " Kent Overstreet
2018-05-22 10:10   ` Javier Gonzalez
2018-05-20 22:25 ` [PATCH 05/12] bcache: " Kent Overstreet
2018-05-21  3:58   ` Coly Li
2018-05-20 22:25 ` [PATCH 06/12] md: " Kent Overstreet
2018-06-01 10:51   ` Arnd Bergmann
2018-05-20 22:25 ` [PATCH 07/12] dm: " Kent Overstreet
2018-05-30 19:27   ` Mike Snitzer
2018-05-20 22:25 ` [PATCH 08/12] target: " Kent Overstreet
2018-05-22 10:09   ` Christoph Hellwig
2018-05-20 22:25 ` [PATCH 09/12] fs: convert block_dev.c to bioset_init() Kent Overstreet
2018-05-22 10:09   ` Christoph Hellwig
2018-05-20 22:25 ` [PATCH 10/12] btrfs: convert to bioset_init()/mempool_init() Kent Overstreet
2018-05-30 21:30   ` Chris Mason
2018-05-20 22:25 ` [PATCH 11/12] xfs: " Kent Overstreet
2018-05-21 18:39   ` Darrick J. Wong
2018-05-22 10:10   ` Christoph Hellwig
2018-05-20 22:25 ` [PATCH 12/12] block: Drop bioset_create() Kent Overstreet
2018-05-22 10:10   ` Christoph Hellwig
2018-05-20 23:08 ` [PATCH 00/13] convert block layer to bioset_init()/mempool_init() NeilBrown
2018-05-20 23:11   ` Kent Overstreet
2018-05-21 14:03 ` Mike Snitzer
2018-05-21 14:19   ` Jens Axboe
2018-05-21 14:31     ` Mike Snitzer
2018-05-21 14:36       ` Jens Axboe
2018-05-21 14:47         ` Mike Snitzer
2018-05-21 14:52           ` Jens Axboe
2018-05-21 15:04             ` Mike Snitzer
2018-05-21 15:09               ` Jens Axboe
2018-05-21 15:18                 ` Mike Snitzer
2018-05-21 15:36                   ` Jens Axboe
2018-05-21 16:09                     ` Mike Snitzer
2018-05-21 16:20                       ` Jens Axboe
2018-05-30 13:36                         ` Mike Snitzer
2018-05-30 18:55                           ` Jens Axboe
2018-05-30 19:34                             ` Kent Overstreet
2018-05-30 19:36                               ` Jens Axboe
2018-05-30 19:37                             ` Mike Snitzer
2018-05-30 19:38                               ` Jens Axboe [this message]
2018-05-21 17:37                       ` Kent Overstreet
2018-05-21 18:24                         ` Mike Snitzer
2018-05-21 23:38                           ` Kent Overstreet
2018-05-22  6:41                             ` Christoph Hellwig
2018-05-22 19:09                               ` Mike Snitzer
2018-05-21 15:12     ` David Sterba
2018-05-21 15:18       ` Jens Axboe
2018-05-21 14:20 ` Jens Axboe
2018-05-30 22:24 ` Jens Axboe

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=5f32b2e7-859b-42f9-c726-115ba5ff22a9@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=bacik@fb.com \
    --cc=clm@fb.com \
    --cc=colyli@suse.de \
    --cc=darrick.wong@oracle.com \
    --cc=drbd-dev@lists.linbit.com \
    --cc=hch@infradead.org \
    --cc=kent.overstreet@gmail.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=neilb@suse.com \
    --cc=snitzer@redhat.com \
    /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 NNTP newsgroup(s).