[dm-devel] [PATCH v6 0/2] dax, dm: stop requiring dax for device-mapper
Mike Snitzer
snitzer at redhat.com
Thu Jan 4 18:12:03 UTC 2018
On Wed, Nov 29 2017 at 1:59pm -0500,
Dan Williams <dan.j.williams at intel.com> 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
More information about the dm-devel
mailing list