From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932183AbeE3Teo (ORCPT ); Wed, 30 May 2018 15:34:44 -0400 Received: from mail-qt0-f193.google.com ([209.85.216.193]:35137 "EHLO mail-qt0-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753627AbeE3Tej (ORCPT ); Wed, 30 May 2018 15:34:39 -0400 X-Google-Smtp-Source: ADUXVKI/hqiiN5lnBVcCYgukV5PaT5K04Q1z2IhsotcShvwfmU2544K/zh1/O3/5O4o2w800EDm8Iw== Date: Wed, 30 May 2018 15:34:35 -0400 From: Kent Overstreet To: Jens Axboe Cc: Mike Snitzer , 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() Message-ID: <20180530193435.GC3487@kmo-pixel> References: <20180521144703.GA19303@redhat.com> <4b343aef-e11c-73ba-1d88-7e73ca838cad@kernel.dk> <20180521150439.GA19379@redhat.com> <61e30dcf-a01c-f47d-087a-12930caf9aef@kernel.dk> <20180521151817.GA19454@redhat.com> <20180521160907.GA19553@redhat.com> <20180530133629.GC5157@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.0 (2018-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, May 30, 2018 at 12:55:48PM -0600, Jens Axboe 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 don't have a strong opinion on 4.18 vs. 4.19, but I'm available to do whatever fixups are needed if it'll help get them in faster.