* linux-next: manual merge of the dax-misc tree with the nvdimm tree
@ 2016-05-18 3:34 Stephen Rothwell
0 siblings, 0 replies; only message in thread
From: Stephen Rothwell @ 2016-05-18 3:34 UTC (permalink / raw)
To: Verma, Vishal L; +Cc: linux-next, linux-kernel, Dan Williams, Jan Kara
Hi all,
Today's linux-next merge of the dax-misc tree got a conflict in:
fs/block_dev.c
between commit:
8044aae6f374 ("Revert "block: enable dax for raw block devices"")
from the nvdimm tree and commit:
02fbd139759f ("dax: Remove complete_unwritten argument")
from the dax-misc tree.
I fixed it up (the former removed the code modified by the latter) 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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2016-05-18 3:34 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-05-18 3:34 linux-next: manual merge of the dax-misc 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.