[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAL_JsqKYUOPFS=0rWuUL2HLNz1DdKbYULckAWnCq-0v96-1S4g@mail.gmail.com>
Date: Thu, 28 May 2020 08:14:36 -0600
From: Rob Herring <robherring2@...il.com>
To: Greg KH <greg@...ah.com>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Sandeep Maheswaram <sanm@...eaurora.org>,
Felipe Balbi <balbi@...nel.org>
Subject: Re: linux-next: manual merge of the usb tree with the devicetree tree
On Thu, May 28, 2020 at 4:49 AM Greg KH <greg@...ah.com> wrote:
>
> On Thu, May 28, 2020 at 04:22:15PM +1000, Stephen Rothwell wrote:
> > Hi all,
> >
> > Today's linux-next merge of the usb tree got a conflict in:
> >
> > Documentation/devicetree/bindings/usb/qcom,dwc3.yaml
> >
> > between commit:
> >
> > 3828026c9ec8 ("dt-bindings: usb: qcom,dwc3: Convert USB DWC3 bindings")
> >
> > from the devicetree tree and commits:
> >
> > cd4b54e2ae1f ("dt-bindings: usb: qcom,dwc3: Convert USB DWC3 bindings")
> >
> > from the usb tree.
> >
> > I fixed it up (I guessed, taking most changes from the former) 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.
Ugg, I fixed up a warning on my side...
>
> Sounds good,t hanks.
Greg, can you revert your copy and we can get rid of the conflict.
Rob
Powered by blists - more mailing lists