From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
David Miller <davem@davemloft.net>,
netdev@vger.kernel.org, Olof Johansson <olof@lixom.net>,
Florian Fainelli <f.fainelli@gmail.com>,
Pramod Kumar <pramod.kumar@broadcom.com>,
linux-kernel@vger.kernel.org,
Yendapally Reddy Dhananjaya Reddy
<yendapally.reddy@broadcom.com>,
linux-next@vger.kernel.org, Jon Mason <jon.mason@broadcom.com>
Subject: Re: linux-next: manual merge of the net-next tree with the arm-soc tree
Date: Tue, 21 Jun 2016 10:56:21 +0200 [thread overview]
Message-ID: <4384645.F021K1OoaK@wuerfel> (raw)
In-Reply-To: <20160621111839.34936836@canb.auug.org.au>
On Tuesday, June 21, 2016 11:18:39 AM CEST Stephen Rothwell wrote:
> Today's linux-next merge of the net-next tree got conflicts in:
>
> arch/arm64/boot/dts/broadcom/ns2-svk.dts
> arch/arm64/boot/dts/broadcom/ns2.dtsi
>
> between commits:
>
> 97b1504a30b3 ("arm64: dts: enable pinctrl for Broadcom NS2 SoC")
> 5dcc9c7618df ("arm64: dts: NS2: Add CCI-400 PMU support")
>
> from the arm-soc tree and commit:
>
> 5f1a067bfa0a ("dt: mdio-mux: Add mdio multiplexer driver node")
>
> from the net-next 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 to me, thanks!
I don't see a good way to resolve the conflict before the merge window,
but it's simple enough that we can just send it this way and let
Linus handle it.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: linux-next: manual merge of the net-next tree with the arm-soc tree
Date: Tue, 21 Jun 2016 10:56:21 +0200 [thread overview]
Message-ID: <4384645.F021K1OoaK@wuerfel> (raw)
In-Reply-To: <20160621111839.34936836@canb.auug.org.au>
On Tuesday, June 21, 2016 11:18:39 AM CEST Stephen Rothwell wrote:
> Today's linux-next merge of the net-next tree got conflicts in:
>
> arch/arm64/boot/dts/broadcom/ns2-svk.dts
> arch/arm64/boot/dts/broadcom/ns2.dtsi
>
> between commits:
>
> 97b1504a30b3 ("arm64: dts: enable pinctrl for Broadcom NS2 SoC")
> 5dcc9c7618df ("arm64: dts: NS2: Add CCI-400 PMU support")
>
> from the arm-soc tree and commit:
>
> 5f1a067bfa0a ("dt: mdio-mux: Add mdio multiplexer driver node")
>
> from the net-next 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 to me, thanks!
I don't see a good way to resolve the conflict before the merge window,
but it's simple enough that we can just send it this way and let
Linus handle it.
Arnd
next prev parent reply other threads:[~2016-06-21 8:55 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-21 1:18 linux-next: manual merge of the net-next tree with the arm-soc tree Stephen Rothwell
2016-06-21 1:18 ` Stephen Rothwell
2016-06-21 1:18 ` Stephen Rothwell
2016-06-21 1:18 ` Stephen Rothwell
2016-06-21 8:56 ` Arnd Bergmann [this message]
2016-06-21 8:56 ` Arnd Bergmann
2016-06-21 8:56 ` Arnd Bergmann
-- strict thread matches above, loose matches on Subject: below --
2022-07-13 2:55 Stephen Rothwell
2022-07-13 2:55 ` Stephen Rothwell
2021-02-16 2:04 Stephen Rothwell
2021-02-16 2:04 ` Stephen Rothwell
2021-02-16 2:20 ` nobuhiro1.iwamatsu
2021-02-16 2:20 ` nobuhiro1.iwamatsu
2021-02-16 10:11 ` Arnd Bergmann
2021-02-16 10:11 ` Arnd Bergmann
2021-02-16 11:53 ` Yoshihiro Shimoda
2021-02-16 11:53 ` Yoshihiro Shimoda
2021-02-16 12:28 ` Naresh Kamboju
2021-02-16 12:28 ` Naresh Kamboju
2021-02-16 13:47 ` nobuhiro1.iwamatsu
2021-02-16 13:47 ` nobuhiro1.iwamatsu
2021-02-16 14:21 ` nobuhiro1.iwamatsu
2021-02-16 14:21 ` nobuhiro1.iwamatsu
2021-02-16 21:17 ` Stephen Rothwell
2021-02-16 21:17 ` Stephen Rothwell
2021-02-17 0:23 ` Yoshihiro Shimoda
2021-02-17 0:23 ` Yoshihiro Shimoda
2019-09-05 3:42 Stephen Rothwell
2019-09-05 3:42 ` Stephen Rothwell
2016-12-01 1:31 Stephen Rothwell
2016-12-01 1:31 ` Stephen Rothwell
2016-12-01 1:31 ` Stephen Rothwell
2016-07-27 2:53 Stephen Rothwell
2016-07-27 2:53 ` Stephen Rothwell
2016-07-27 2:53 ` Stephen Rothwell
2016-07-27 20:41 ` Duc Dang
2016-07-27 20:41 ` Duc Dang
2016-05-10 0:18 Stephen Rothwell
2016-05-10 0:18 ` Stephen Rothwell
2016-05-10 0:18 ` Stephen Rothwell
2015-01-27 2:04 Stephen Rothwell
2015-01-27 2:04 ` Stephen Rothwell
2015-01-27 2:04 ` Stephen Rothwell
2014-09-25 2:58 Stephen Rothwell
2014-09-25 2:58 ` Stephen Rothwell
2014-09-25 2:58 ` Stephen Rothwell
2014-09-10 4:48 Stephen Rothwell
2014-09-10 4:48 ` Stephen Rothwell
2014-09-10 4:48 ` Stephen Rothwell
2014-09-10 8:06 ` Arnd Bergmann
2014-09-10 8:06 ` Arnd Bergmann
2014-03-31 2:24 Stephen Rothwell
2014-03-31 2:24 ` Stephen Rothwell
2014-03-31 2:24 ` Stephen Rothwell
2012-01-04 4:06 Stephen Rothwell
2012-01-04 4:06 ` Stephen Rothwell
2012-01-04 4:06 ` Stephen Rothwell
2012-01-04 4:06 ` Stephen Rothwell
2012-01-04 4:46 ` Richard Zhao
2012-01-04 4:46 ` Richard Zhao
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=4384645.F021K1OoaK@wuerfel \
--to=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=jon.mason@broadcom.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olof@lixom.net \
--cc=pramod.kumar@broadcom.com \
--cc=sfr@canb.auug.org.au \
--cc=yendapally.reddy@broadcom.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.