* linux-next: manual merge of the akpm tree with the nvdimm tree
@ 2018-04-05 6:30 Stephen Rothwell
0 siblings, 0 replies; only message in thread
From: Stephen Rothwell @ 2018-04-05 6:30 UTC (permalink / raw)
To: Andrew Morton, Dan Williams
Cc: Linux-Next Mailing List, Linux Kernel Mailing List, Matthew Wilcox
[-- Attachment #1: Type: text/plain, Size: 749 bytes --]
Hi Andrew,
Today's linux-next merge of the akpm tree got a conflict in:
fs/dax.c
between commit:
fab6964f22b9 ("mm, fs, dax: handle layout changes to pinned dax mappings")
which was removed from the nvdimm tree today and patch:
"page cache: use xa_lock"
from the akpm tree.
I fixed it up (I removed the dax_layout_busy_page() function) and can
carry the fix as necessary. This is now fixed as far as linux-next is
concerned, but any non trivial conflicts should be mentioned to your
upstream maintainer when your tree is submitted for merging. You may
also want to consider cooperating with the maintainer of the conflicting
tree to minimise any particularly complex conflicts.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2018-04-05 6:31 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-04-05 6:30 linux-next: manual merge of the akpm tree with the nvdimm tree Stephen Rothwell
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.