linux-next: manual merge of the metag tree with Linus' tree

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

 



Hi James,

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

  arch/metag/include/asm/uaccess.h

between commit:

  db68ce10c4f0 ("new helper: uaccess_kernel(new helper: uaccess_kernel())")

from Linus' tree and commit:

  8a8b56638bca ("metag/uaccess: Fix access_ok()")

from the metag tree.

I fixed it up (I used the metag version (as suggested by James, thanks)
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