Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1604178 > unrolled thread

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

Started byStephen Rothwell <sfr@canb.auug.org.au>
First post2017-03-20 06:20 +0100
Last post2017-03-20 06:20 +0100
Articles 1 — 1 participant

Back to article view | Back to linux.kernel


Contents

  linux-next: manual merge of the akpm tree with the net-next tree Stephen Rothwell <sfr@canb.auug.org.au> - 2017-03-20 06:20 +0100

#1604178 — linux-next: manual merge of the akpm tree with the net-next tree

FromStephen Rothwell <sfr@canb.auug.org.au>
Date2017-03-20 06:20 +0100
Subjectlinux-next: manual merge of the akpm tree with the net-next tree
Message-ID<tmXTz-8lw-3@gated-at.bofh.it>
Hi Andrew,

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

  Documentation/devicetree/bindings/net/brcm,unimac-mdio.txt

between commit:

  0ce5aa1d6c97 ("dt-bindings: net: update bcmgenet binding for GENETv5")

from the net-next tree and patch:

  "scripts/spelling.txt: Add regsiter -> register spelling mistake"

from the akpm tree.

I fixed it up (the former also fixed the typo from the latter, so I just
used that) 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

[toc] | [standalone]


Back to top | Article view | linux.kernel


csiph-web