linux-next: manual merge of the fscache tree with the asm-generic tree

[Stephen Rothwell]

Hi all,

Today's linux-next merge of the fscache tree got a conflict in:

  fs/fscache/proc.c

between commit:

  5c61c384095a ("Documentation, arch, fs: Remove leftovers from fscache object list")

from the asm-generic tree and commit:

  8ed89a0cad0c ("fscache: Introduce new driver")

from the fscache tree.

I fixed it up (I just used the latter 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

Attachment: pgpy8gai0Foqf.pgp
Description: OpenPGP digital signature