On Fri, Apr 21, 2017 at 6:06 PM, Dan Williams <dan.j.williams@xxxxxxxxx> wrote: > [ adding akpm, sfr, and jens ] > > I applied this series and pushed it out for the nvdimm.git branch that > gets auto pulled into -next. The set is still awaiting acks from > device-mapper, ext4, xfs, and vfs (for the copy_from_iter_ops, patch > 29/33). If those come next week perhaps this can be merged for 4.12, > but if not this will need to wait until 4.13. > > There are some minor collisions with Al's copy_from_user rework, the > new dax tracepoints, and the removal of discard support from the brd > driver. A sample merge is available here: > > https://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm.git/log/?h=libnvdimm-for-4.12-merge > > If it causes any other problems just drop and I'll retry for 4.13. Al has nak'd the uaccess related changes, and I'll need to rework those patches to move the pmem routines into lib/iov_iter.c directly. That doesn't affect the dax_device and dax_operations work, so I'm still looking to move forward with that change. That reduces the set targeting 4.12 to just the first 18 patches from this series: Dan Williams (18): device-dax: rename 'dax_dev' to 'dev_dax' dax: refactor dax-fs into a generic provider of 'struct dax_device' instances dax: add a facility to lookup a dax device by 'host' device name dax: introduce dax_operations pmem: add dax_operations support axon_ram: add dax_operations support brd: add dax_operations support dcssblk: add dax_operations support block: kill bdev_dax_capable() dax: introduce dax_direct_access() dm: add dax_device and dax_operations support dm: teach dm-targets to use a dax_device + dax_operations ext2, ext4, xfs: retrieve dax_device for iomap operations Revert "block: use DAX for partition table reads" filesystem-dax: convert to dax_direct_access() block, dax: convert bdev_dax_supported() to dax_direct_access() block: remove block_device_operations ->direct_access() x86, dax, pmem: remove indirection around memcpy_from_pmem() -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
