On Wed, Aug 02 2017 at 1:57pm -0400, Dan Williams <dan.j.williams@xxxxxxxxx> wrote: > 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. Commit 273752c9ff03eb83856601b2a3458218bb949e46 is upstream as of v4.13-rc3 -- so no real need to have this go via linux-dm.git That said, I don't mind picking it up once we are satisfied with the implementation. I'll start reviewing shortly. Mike -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
