[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <2023101818-recant-goldfish-44b0@gregkh>
Date: Wed, 18 Oct 2023 09:56:27 +0200
From: Greg KH <greg@...ah.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Rob Herring <robh@...nel.org>,
Abdel Alkuor <abdelalkuor@...tab.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: manual merge of the usb tree with the devicetree tree
On Wed, Oct 18, 2023 at 01:13:34PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the usb tree got a conflict in:
>
> Documentation/devicetree/bindings/usb/ti,tps6598x.yaml
>
> between commit:
>
> 47b8fb4aef95 ("dt-bindings: usb: ti,tps6598x: Disallow undefined properties")
>
> from the devicetree tree and commit:
>
> 6060d554e891 ("dt-bindings: usb: tps6598x: Add tps25750")
>
> from the usb 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.
Looks good, thanks!
greg k-h
Powered by blists - more mailing lists