* linux-next: manual merge of the devicetree tree with the renesas tree
@ 2017-06-09 3:53 Stephen Rothwell
2017-06-09 13:46 ` Rob Herring
2017-06-09 16:01 ` Simon Horman
0 siblings, 2 replies; 4+ messages in thread
From: Stephen Rothwell @ 2017-06-09 3:53 UTC (permalink / raw)
To: Rob Herring, Simon Horman
Cc: Linux-Next Mailing List, Linux Kernel Mailing List,
Marcus Cooper, Biju Das
Hi Rob,
Today's linux-next merge of the devicetree tree got a conflict in:
Documentation/devicetree/bindings/vendor-prefixes.txt
between commit:
d795f15618b8 ("of: Add vendor prefix for iWave Systems Technologies Pvt. Ltd")
from the renesas tree and commit:
97a0268e764c ("devicetree: add Itead vendor prefix")
from the devicetree tree.
I fixed it up (see below) 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
diff --cc Documentation/devicetree/bindings/vendor-prefixes.txt
index b946fc4b172a,b81092afe76d..000000000000
--- a/Documentation/devicetree/bindings/vendor-prefixes.txt
+++ b/Documentation/devicetree/bindings/vendor-prefixes.txt
@@@ -158,7 -159,7 +159,8 @@@ iom Iomega Corporatio
isee ISEE 2007 S.L.
isil Intersil
issi Integrated Silicon Solutions Inc.
+ itead ITEAD Intelligent Systems Co.Ltd
+iwave iWave Systems Technologies Pvt. Ltd.
jdi Japan Display Inc.
jedec JEDEC Solid State Technology Association
karo Ka-Ro electronics GmbH
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: linux-next: manual merge of the devicetree tree with the renesas tree
2017-06-09 3:53 linux-next: manual merge of the devicetree tree with the renesas tree Stephen Rothwell
@ 2017-06-09 13:46 ` Rob Herring
2017-06-12 9:58 ` Simon Horman
2017-06-09 16:01 ` Simon Horman
1 sibling, 1 reply; 4+ messages in thread
From: Rob Herring @ 2017-06-09 13:46 UTC (permalink / raw)
To: Stephen Rothwell, Simon Horman
Cc: Linux-Next Mailing List, Linux Kernel Mailing List,
Marcus Cooper, Biju Das
On Thu, Jun 8, 2017 at 10:53 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi Rob,
>
> Today's linux-next merge of the devicetree tree got a conflict in:
>
> Documentation/devicetree/bindings/vendor-prefixes.txt
>
> between commit:
>
> d795f15618b8 ("of: Add vendor prefix for iWave Systems Technologies Pvt. Ltd")
>
> from the renesas tree and commit:
>
> 97a0268e764c ("devicetree: add Itead vendor prefix")
>
> from the devicetree tree.
>
> I fixed it up (see below) 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.
Simon, I can pick up the conflicting patch if you want to drop it.
Rob
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: linux-next: manual merge of the devicetree tree with the renesas tree
2017-06-09 3:53 linux-next: manual merge of the devicetree tree with the renesas tree Stephen Rothwell
2017-06-09 13:46 ` Rob Herring
@ 2017-06-09 16:01 ` Simon Horman
1 sibling, 0 replies; 4+ messages in thread
From: Simon Horman @ 2017-06-09 16:01 UTC (permalink / raw)
To: Stephen Rothwell
Cc: Rob Herring, Linux-Next Mailing List, Linux Kernel Mailing List,
Marcus Cooper, Biju Das
On Fri, Jun 09, 2017 at 01:53:04PM +1000, Stephen Rothwell wrote:
> Hi Rob,
>
> Today's linux-next merge of the devicetree tree got a conflict in:
>
> Documentation/devicetree/bindings/vendor-prefixes.txt
>
> between commit:
>
> d795f15618b8 ("of: Add vendor prefix for iWave Systems Technologies Pvt. Ltd")
>
> from the renesas tree and commit:
>
> 97a0268e764c ("devicetree: add Itead vendor prefix")
>
> from the devicetree tree.
>
> I fixed it up (see below) 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.
Thanks Stephen, the merge looks correct to me.
Rob, would you prefer if this patch was not merged through my renesas tree?
>
> --
> Cheers,
> Stephen Rothwell
>
> diff --cc Documentation/devicetree/bindings/vendor-prefixes.txt
> index b946fc4b172a,b81092afe76d..000000000000
> --- a/Documentation/devicetree/bindings/vendor-prefixes.txt
> +++ b/Documentation/devicetree/bindings/vendor-prefixes.txt
> @@@ -158,7 -159,7 +159,8 @@@ iom Iomega Corporatio
> isee ISEE 2007 S.L.
> isil Intersil
> issi Integrated Silicon Solutions Inc.
> + itead ITEAD Intelligent Systems Co.Ltd
> +iwave iWave Systems Technologies Pvt. Ltd.
> jdi Japan Display Inc.
> jedec JEDEC Solid State Technology Association
> karo Ka-Ro electronics GmbH
>
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: linux-next: manual merge of the devicetree tree with the renesas tree
2017-06-09 13:46 ` Rob Herring
@ 2017-06-12 9:58 ` Simon Horman
0 siblings, 0 replies; 4+ messages in thread
From: Simon Horman @ 2017-06-12 9:58 UTC (permalink / raw)
To: Rob Herring
Cc: Stephen Rothwell, Linux-Next Mailing List,
Linux Kernel Mailing List, Marcus Cooper, Biju Das
On Fri, Jun 09, 2017 at 08:46:27AM -0500, Rob Herring wrote:
> On Thu, Jun 8, 2017 at 10:53 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > Hi Rob,
> >
> > Today's linux-next merge of the devicetree tree got a conflict in:
> >
> > Documentation/devicetree/bindings/vendor-prefixes.txt
> >
> > between commit:
> >
> > d795f15618b8 ("of: Add vendor prefix for iWave Systems Technologies Pvt. Ltd")
> >
> > from the renesas tree and commit:
> >
> > 97a0268e764c ("devicetree: add Itead vendor prefix")
> >
> > from the devicetree tree.
> >
> > I fixed it up (see below) 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.
>
> Simon, I can pick up the conflicting patch if you want to drop it.
Thanks, I will drop it.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2017-06-12 9:58 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-06-09 3:53 linux-next: manual merge of the devicetree tree with the renesas tree Stephen Rothwell
2017-06-09 13:46 ` Rob Herring
2017-06-12 9:58 ` Simon Horman
2017-06-09 16:01 ` Simon Horman
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).