linux-next: manual merge of the akpm tree with the fscrypt tree

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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
--
To unsubscribe from this list: send the line "unsubscribe linux-next" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux Kernel]     [Linux USB Development]     [Yosemite News]     [Linux SCSI]

  Powered by Linux