Re: [PATCH 31/52] dax: Pass dax_dev to dax_writeback_mapping_range()

Hi Vivek, I love your patch! Perhaps something to improve: [auto build test WARNING on fuse/for-next] [also build test WARNING on v4.20-rc6] [cannot apply to next-20181211] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH 31/52] dax: Pass dax_dev to dax_writeback_mapping_range()

Hi Vivek, I love your patch! Yet something to improve: [auto build test ERROR on fuse/for-next] [also build test ERROR on v4.20-rc6] [cannot apply to next-20181210] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

[PATCH 31/52] dax: Pass dax_dev to dax_writeback_mapping_range()

Right now dax_writeback_mapping_range() is passed a bdev and dax_dev is searched from that bdev name. virtio-fs does not have a bdev. So pass in dax_dev also to dax_writeback_mapping_range(). If dax_dev is passed in, bdev is not used otherwise dax_dev is searched using bdev. Signed-off-by: Vivek