Changes since v2 [1]: * rebase on -next to integrate with commit 273752c9ff03 "dm, dax: Make sure dm_dax_flush() is called if device supports it" (kbuild robot) * fix CONFIG_DAX dependencies to upgrade CONFIG_DAX=m to CONFIG_DAX=y (kbuild robot) [1]: https://www.spinics.net/lists/kernel/msg2570522.html --- 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. Since this depends on commit 273752c9ff03 that's already in -next, this should go through the device-mapper tree. --- Dan Williams (2): dax: introduce CONFIG_DAX_DRIVER dm: allow device-mapper to operate without dax support arch/powerpc/platforms/Kconfig | 1 + drivers/block/Kconfig | 1 + drivers/dax/Kconfig | 4 +++- drivers/md/Kconfig | 2 +- drivers/md/dm-linear.c | 6 ++++++ drivers/md/dm-stripe.c | 6 ++++++ drivers/md/dm.c | 10 ++++++---- drivers/nvdimm/Kconfig | 1 + drivers/s390/block/Kconfig | 1 + include/linux/dax.h | 30 ++++++++++++++++++++++++------ 10 files changed, 50 insertions(+), 12 deletions(-) -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
