Vivek Goyal 273752c9ff dm, dax: Make sure dm_dax_flush() is called if device supports it ... Currently dm_dax_flush() is not being called, even if underlying dax device supports write cache, because DAXDEV_WRITE_CACHE is not being propagated up to the DM dax device. If the underlying dax device supports write cache, set DAXDEV_WRITE_CACHE on the DM dax device. This will cause dm_dax_flush() to be called. Fixes: abebfbe2f7 ("dm: add ->flush() dax operation support") Signed-off-by: Vivek Goyal <vgoyal@redhat.com> Acked-by: Dan Williams <dan.j.williams@intel.com> Signed-off-by: Mike Snitzer <snitzer@redhat.com>		2017-07-26 15:55:44 -04:00
..
dax-private.h	Merge branch 'for-4.12/dax' into libnvdimm-for-next	2017-05-04 23:38:43 -07:00
dax.h	pmem: add dax_operations support	2017-04-19 15:14:35 -07:00
device-dax.h	dax: refactor dax-fs into a generic provider of 'struct dax_device' instances	2017-04-12 21:59:14 -07:00
device.c	fs: new infrastructure for writeback error handling and reporting	2017-07-06 07:02:25 -04:00
Kconfig	device-dax: kill NR_DEV_DAX	2017-05-09 09:08:22 -07:00
Makefile	dax: refactor dax-fs into a generic provider of 'struct dax_device' instances	2017-04-12 21:59:14 -07:00
pmem.c	libnvdimm for 4.12	2017-05-05 18:49:20 -07:00
super.c	dm, dax: Make sure dm_dax_flush() is called if device supports it	2017-07-26 15:55:44 -04:00