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. --- Dan Williams (2): dax: introduce CONFIG_DAX_DRIVER dm: allow device-mapper to operate without dax support arch/powerpc/platforms/Kconfig | 2 - drivers/dax/Kconfig | 5 ++ drivers/md/Kconfig | 1 drivers/md/dm-linear.c | 6 +++ drivers/md/dm-log-writes.c | 95 +++++++++++++++++++++------------------- drivers/md/dm-stripe.c | 6 +++ drivers/md/dm.c | 10 +++- drivers/nvdimm/Kconfig | 2 - drivers/s390/block/Kconfig | 2 - include/linux/dax.h | 30 ++++++++++--- 10 files changed, 99 insertions(+), 60 deletions(-) -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
