On Thu, Jan 4, 2018 at 10:12 AM, Mike Snitzer <snitzer(a)redhat.com> wrote:
On Wed, Nov 29 2017 at 1:59pm -0500,
Dan Williams <dan.j.williams(a)intel.com> wrote:
> Changes since v5 :
> * Make DAX_DRIVER select DAX to simplify the Kconfig dependencies
> * Rebase on 4.15-rc1 and add new IS_ENABLED(CONFIG_DAX_DRIVER) checks in
> : 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.
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.
There might be some more collisions as we are going to kill the DAX
support in axonram and dcssblk. If I get your reviewed-by on these
I'll take them through the nvdimm tree.