2021-06-22 08:17:30

by Stephen Rothwell

[permalink] [raw]
Subject: linux-next: manual merge of the gpio-brgl tree with the devicetree tree

Hi all,

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

Documentation/devicetree/bindings/gpio/gpio-davinci.txt

between commit:

c601eef1e258 ("dt-bindings: clock: update ti,sci-clk.yaml references")

from the devicetree tree and commit:

c830b87a761b ("dt-bindings: gpio: gpio-davinci: Convert to json-schema")

from the gpio-brgl tree.

I fixed it up (the latter 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


Attachments:
(No filename) (499.00 B)
OpenPGP digital signature

2021-06-23 17:28:02

by Rob Herring

[permalink] [raw]
Subject: Re: linux-next: manual merge of the gpio-brgl tree with the devicetree tree

On Tue, Jun 22, 2021 at 2:16 AM Stephen Rothwell <[email protected]> wrote:
>
> Hi all,
>
> Today's linux-next merge of the gpio-brgl tree got a conflict in:
>
> Documentation/devicetree/bindings/gpio/gpio-davinci.txt
>
> between commit:
>
> c601eef1e258 ("dt-bindings: clock: update ti,sci-clk.yaml references")
>
> from the devicetree tree and commit:
>
> c830b87a761b ("dt-bindings: gpio: gpio-davinci: Convert to json-schema")
>
> from the gpio-brgl tree.
>
> I fixed it up (the latter removed the file, so I did that) and can
> carry the fix as necessary.

As the reference is gone in the schema, that is the correct resolution.

Rob