public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Kishon Vijay Abraham I <kishon@ti.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Douglas Anderson <dianders@chromium.org>,
	Evan Green <evgreen@chromium.org>
Subject: Re: linux-next: manual merge of the phy-next tree with Linus' tree
Date: Wed, 12 Dec 2018 10:37:37 +0530	[thread overview]
Message-ID: <c868398c-9410-fa2d-26f4-dd86102a3584@ti.com> (raw)
In-Reply-To: <20181212151647.71a5befe@canb.auug.org.au>

Hi,

On 12/12/18 9:46 AM, Stephen Rothwell wrote:
> Hi all,
> 
> Today's linux-next merge of the phy-next tree got a conflict in:
> 
>   Documentation/devicetree/bindings/phy/qcom-qmp-phy.txt
> 
> between commit:
> 
>   7243ec72b902 ("dt-bindings: phy-qcom-qmp: Fix several mistakes from prior commits")
> 
> from Linus' tree and commit:
> 
>   91fdc9b127c9 ("dt-bindings: phy-qcom-qmp: Fix register underspecification")
> 
> from the phy-next tree.
> 
> I fixed it up (I just used the latter veriosn of the conflicting line)
> 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.

I've rebased by 'next' branch on top of my 'fixes' branch to avoid this conflict.

Thanks
Kishon
> 

  reply	other threads:[~2018-12-12  5:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-12  4:16 linux-next: manual merge of the phy-next tree with Linus' tree Stephen Rothwell
2018-12-12  5:07 ` Kishon Vijay Abraham I [this message]
2018-12-12  5:12   ` Stephen Rothwell
2018-12-12  5:28     ` Kishon Vijay Abraham I

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c868398c-9410-fa2d-26f4-dd86102a3584@ti.com \
    --to=kishon@ti.com \
    --cc=dianders@chromium.org \
    --cc=evgreen@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox