Hi, [This is an automated email]
This commit has been processed because it contains a "Fixes:" tag, fixing commit: 004f1afbe199 libnvdimm, pmem: direct map legacy pmem by default. The bot has tested the following trees: v4.20.8, v4.19.21, v4.14.99, v4.9.156, v4.4.174. v4.20.8: Build OK! v4.19.21: Build OK! v4.14.99: Build OK! v4.9.156: Build OK! v4.4.174: Failed to apply! Possible dependencies: 0caeef63e6d2 ("libnvdimm: Add a poison list and export badblocks") 0e749e54244e ("dax: increase granularity of dax_clear_blocks() operations") 34c0fd540e79 ("mm, dax, pmem: introduce pfn_t") 4b94ffdc4163 ("x86, mm: introduce vmem_altmap to augment vmemmap_populate()") 52db400fcd50 ("pmem, dax: clean up clear_pmem()") 87ba05dff351 ("libnvdimm: don't fail init for full badblocks list") 9476df7d80df ("mm: introduce find_dev_pagemap()") ad9a8bde2cb1 ("libnvdimm, pmem: move definition of nvdimm_namespace_add_poison to nd.h") b2e0d1625e19 ("dax: fix lifetime of in-kernel dax mappings with dax_map_atomic()") b95f5f4391fa ("libnvdimm: convert to statically allocated badblocks") cfe30b872058 ("libnvdimm, pmem: adjust for section collisions with 'System RAM'") d2c0f041e1bb ("libnvdimm, pfn, pmem: allocate memmap array in persistent memory") d9cbe09d39aa ("libnvdimm, pmem: fix 'pfn' support for section-misaligned namespaces") How should we proceed with this patch? -- Thanks, Sasha _______________________________________________ Linux-nvdimm mailing list Linux-nvdimm@lists.01.org https://lists.01.org/mailman/listinfo/linux-nvdimm