From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mike Snitzer Subject: Re: [PATCH v6 0/2] dax, dm: stop requiring dax for device-mapper Date: Thu, 4 Jan 2018 13:12:03 -0500 Message-ID: <20180104181202.GA14491@redhat.com> References: <151198199487.7051.7083189934624068090.stgit@dwillia2-desk3.amr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <151198199487.7051.7083189934624068090.stgit@dwillia2-desk3.amr.corp.intel.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dm-devel-bounces@redhat.com Errors-To: dm-devel-bounces@redhat.com To: Dan Williams Cc: kbuild test robot , linux-nvdimm@lists.01.org, Michael Ellerman , Heiko Carstens , Martin Schwidefsky , dm-devel@redhat.com, Paul Mackerras , Alasdair Kergon , Benjamin Herrenschmidt , Bart Van Assche , Gerald Schaefer List-Id: dm-devel.ids On Wed, Nov 29 2017 at 1:59pm -0500, Dan Williams wrote: > Changes since v5 [1]: > * Make DAX_DRIVER select DAX to simplify the Kconfig dependencies > (Michael) > * Rebase on 4.15-rc1 and add new IS_ENABLED(CONFIG_DAX_DRIVER) checks in > drivers/md/dm-log-writes.c. > > [1]: https://lists.01.org/pipermail/linux-nvdimm/2017-September/012569.html > > --- > > Hi Mike, > > Bart points out that the DAX core is unconditionally enabled if > device-mapper is enabled. Add some config machinery and some > stub/static-inline routines to allow dax infrastructure to be deleted > from device-mapper at compile time. Hey Dan, Did you want me to pick this up for 4.16 or were you thinking of sending the changes through a different tree? I'm fine with picking these up so long as you don't expect the dax.h and Kconfig changes to become a source of conflict come merge time. Let me know, thanks! Mike From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 36CD521F833D6 for ; Thu, 4 Jan 2018 10:07:03 -0800 (PST) Date: Thu, 4 Jan 2018 13:12:03 -0500 From: Mike Snitzer Subject: Re: [PATCH v6 0/2] dax, dm: stop requiring dax for device-mapper Message-ID: <20180104181202.GA14491@redhat.com> References: <151198199487.7051.7083189934624068090.stgit@dwillia2-desk3.amr.corp.intel.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <151198199487.7051.7083189934624068090.stgit@dwillia2-desk3.amr.corp.intel.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: linux-nvdimm-bounces@lists.01.org Sender: "Linux-nvdimm" To: Dan Williams Cc: kbuild test robot , linux-nvdimm@lists.01.org, Michael Ellerman , Heiko Carstens , Martin Schwidefsky , dm-devel@redhat.com, Paul Mackerras , Alasdair Kergon , Benjamin Herrenschmidt , Bart Van Assche , Gerald Schaefer List-ID: On Wed, Nov 29 2017 at 1:59pm -0500, Dan Williams wrote: > Changes since v5 [1]: > * Make DAX_DRIVER select DAX to simplify the Kconfig dependencies > (Michael) > * Rebase on 4.15-rc1 and add new IS_ENABLED(CONFIG_DAX_DRIVER) checks in > drivers/md/dm-log-writes.c. > > [1]: https://lists.01.org/pipermail/linux-nvdimm/2017-September/012569.html > > --- > > Hi Mike, > > Bart points out that the DAX core is unconditionally enabled if > device-mapper is enabled. Add some config machinery and some > stub/static-inline routines to allow dax infrastructure to be deleted > from device-mapper at compile time. Hey Dan, Did you want me to pick this up for 4.16 or were you thinking of sending the changes through a different tree? I'm fine with picking these up so long as you don't expect the dax.h and Kconfig changes to become a source of conflict come merge time. Let me know, thanks! Mike _______________________________________________ Linux-nvdimm mailing list Linux-nvdimm@lists.01.org https://lists.01.org/mailman/listinfo/linux-nvdimm