Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1727129 > unrolled thread
| Started by | Stephen Rothwell <sfr@canb.auug.org.au> |
|---|---|
| First post | 2017-09-06 05:10 +0200 |
| Last post | 2017-09-06 05:10 +0200 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.kernel
linux-next: manual merge of the devicetree tree with Linus' tree Stephen Rothwell <sfr@canb.auug.org.au> - 2017-09-06 05:10 +0200
| From | Stephen Rothwell <sfr@canb.auug.org.au> |
|---|---|
| Date | 2017-09-06 05:10 +0200 |
| Subject | linux-next: manual merge of the devicetree tree with Linus' tree |
| Message-ID | <umyT0-3GR-15@gated-at.bofh.it> |
Hi Rob,
Today's linux-next merge of the devicetree tree got a conflict in:
Documentation/devicetree/bindings/net/brcm,bgmac-nsp.txt
between commit:
ea6c3077678f ("dt-bindings: net: Remove duplicate NSP Ethernet MAC binding document")
from Linus' tree and commit:
4da722ca19f3 ("dt-bindings: Remove "status" from examples")
from the devicetree tree.
I fixed it up (the former removed the file, so I did 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
Back to top | Article view | linux.kernel
csiph-web