[lkml]   [2019]   [Jun]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Subjectlinux-next: manual merge of the mfd tree with Linus' tree
Hi all,

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


between commit:

9c92ab619141 ("treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 282")

from Linus' tree and commit:

2769bd79a915 ("mfd: cros_ec: Update license term")

from the mfd tree.

I fixed it up (I use the SPDX tag from the former and the later change
to the comment from 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.

Stephen Rothwell
[unhandled content-type:application/pgp-signature]
 \ /
  Last update: 2019-06-11 06:32    [W:0.032 / U:0.096 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site