* linux-next: manual merge of the akpm tree with the fscrypt tree
@ 2018-02-02 3:17 Stephen Rothwell
0 siblings, 0 replies; only message in thread
From: Stephen Rothwell @ 2018-02-02 3:17 UTC (permalink / raw)
To: Andrew Morton, Theodore Ts'o
Cc: Linux-Next Mailing List, Linux Kernel Mailing List, Eric Biggers
Hi Andrew,
Today's linux-next merge of the akpm tree got a conflict in:
fs/crypto/hooks.c
between commit:
0b1dfa4cc6c6 ("fscrypt: fix build with pre-4.6 gcc versions")
from the fscrypt tree and patch:
"fs/crypto/hooks.c: fix build with gcc-4.4.4"
from the akpm tree.
I fixed it up (I just dropped the akpm tree version) 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:[~2018-02-02 3:17 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-02-02 3:17 linux-next: manual merge of the akpm tree with the fscrypt 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.