summaryrefslogtreecommitdiff
path: root/.mailmap
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2017-01-21 18:53:06 -0800
committerLinus Torvalds <torvalds@linux-foundation.org>2017-01-21 18:53:06 -0800
commitf68d8531cceabb6683a8f949d2d933cd854da141 (patch)
treee2b073a18bd30945c2f2ead0ba79d721be99b6bf /.mailmap
parentf5e8c0ff563e6bf1633e5a35b0d9b8fe4c7560b8 (diff)
parent1f19b983a8877f81763fab3e693c6befe212736d (diff)
Merge branch 'libnvdimm-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm
Pull libnvdimm fixes from Dan Williams: "Two fixes: - a regression fix for the multiple-pmem-namespace-per-region support added in 4.9. Even if an existing environment is not using that feature the act of creating and a destroying a single namespace with the ndctl utility will lead to the proliferation of extra unwanted namespace devices. - a fix for the error code returned from the pmem driver when the memcpy_mcsafe() routine returns -EFAULT. Btrfs seems to be the only block I/O consumer that tries to parse the meaning of the error code when it is non-zero. Neither of these fixes are critical, the namespace leak is awkward in that it can cause device naming to change and complicates debugging namespace initialization issues. The error code fix is included out of caution for what other consumers might be expecting -EIO for block I/O errors" * 'libnvdimm-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm: libnvdimm, namespace: fix pmem namespace leak, delete when size set to zero pmem: return EIO on read_pmem() failure
Diffstat (limited to '.mailmap')
0 files changed, 0 insertions, 0 deletions