diff options
| author | Linus Torvalds <torvalds@linux-foundation.org> | 2016-04-15 15:34:27 -0700 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2016-04-15 15:34:27 -0700 |
| commit | f3c9a1abbe9d4c9565fdb0755e2c7814f32d4f62 (patch) | |
| tree | 14e3ad5ade1e2f1b806fc466f30c1854866e85c4 /drivers/block | |
| parent | 29dde7c25adafcdcbde3a14bce3f07e5a201dc30 (diff) | |
| parent | 0a370d261c805286cbdfa1f96661322a28cce860 (diff) | |
| download | linux-f3c9a1abbe9d4c9565fdb0755e2c7814f32d4f62.tar.gz linux-f3c9a1abbe9d4c9565fdb0755e2c7814f32d4f62.tar.bz2 linux-f3c9a1abbe9d4c9565fdb0755e2c7814f32d4f62.zip | |
Merge branch 'libnvdimm-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm
Pull libnvdimm fixes from Ross Zwisler:
"Two fixes:
- Fix memcpy_from_pmem() to fallback to memcpy() for architectures
where CONFIG_ARCH_HAS_PMEM_API=n.
- Add a comment explaining why we write data twice when clearing
poison in pmem_do_bvec().
This has passed a boot test on an X86_32 config, which was the
architecture where issue #1 above was first noticed"
Dan Williams adds:
"We're giving this multi-maintainer setup a shot, so expect libnvdimm
pull requests from either Ross or I going forward"
* 'libnvdimm-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm:
libnvdimm, pmem: clarify the write+clear_poison+write flow
pmem: fix BUG() error in pmem.h:48 on X86_32
Diffstat (limited to 'drivers/block')
0 files changed, 0 insertions, 0 deletions