linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: David Miller <davem@davemloft.net>,
	Networking <netdev@vger.kernel.org>,
	Heiko Stuebner <heiko@sntech.de>
Cc: Frank Wunderlich <frank-w@public-files.de>,
	Jakub Kicinski <kuba@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: manual merge of the net-next tree with the rockchip tree
Date: Thu, 16 Jun 2022 11:16:35 +1000	[thread overview]
Message-ID: <20220616111635.3e27c15b@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 1964 bytes --]

Hi all,

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

  arch/arm64/boot/dts/rockchip/rk3568-bpi-r2-pro.dts

between commit:

  f48387c005fa ("arm64: dts: rockchip: Enable HDMI audio on BPI R2 Pro")

from the rockchip tree and commit:

  c1804463e5c6 ("arm64: dts: rockchip: Add mt7531 dsa node to BPI-R2-Pro board")

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.

-- 
Cheers,
Stephen Rothwell

diff --cc arch/arm64/boot/dts/rockchip/rk3568-bpi-r2-pro.dts
index 1d3ffbf3cde8,7df8cfb1d3b9..000000000000
--- a/arch/arm64/boot/dts/rockchip/rk3568-bpi-r2-pro.dts
+++ b/arch/arm64/boot/dts/rockchip/rk3568-bpi-r2-pro.dts
@@@ -453,11 -394,54 +453,59 @@@
  	status = "disabled";
  };
  
 +&i2s0_8ch {
 +	/* hdmi sound */
 +	status = "okay";
 +};
 +
+ &mdio0 {
+ 	#address-cells = <1>;
+ 	#size-cells = <0>;
+ 
+ 	switch@0 {
+ 		compatible = "mediatek,mt7531";
+ 		reg = <0>;
+ 
+ 		ports {
+ 			#address-cells = <1>;
+ 			#size-cells = <0>;
+ 
+ 			port@1 {
+ 				reg = <1>;
+ 				label = "lan0";
+ 			};
+ 
+ 			port@2 {
+ 				reg = <2>;
+ 				label = "lan1";
+ 			};
+ 
+ 			port@3 {
+ 				reg = <3>;
+ 				label = "lan2";
+ 			};
+ 
+ 			port@4 {
+ 				reg = <4>;
+ 				label = "lan3";
+ 			};
+ 
+ 			port@5 {
+ 				reg = <5>;
+ 				label = "cpu";
+ 				ethernet = <&gmac0>;
+ 				phy-mode = "rgmii";
+ 
+ 				fixed-link {
+ 					speed = <1000>;
+ 					full-duplex;
+ 					pause;
+ 				};
+ 			};
+ 		};
+ 	};
+ };
+ 
  &mdio1 {
  	rgmii_phy1: ethernet-phy@0 {
  		compatible = "ethernet-phy-ieee802.3-c22";

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2022-06-16  1:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-16  1:16 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-08-28  1:33 linux-next: manual merge of the net-next tree with the rockchip tree Stephen Rothwell
2017-08-22  1:24 Stephen Rothwell
2017-09-04  5:26 ` Stephen Rothwell
2017-08-15  1:52 Stephen Rothwell

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=20220616111635.3e27c15b@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=davem@davemloft.net \
    --cc=frank-w@public-files.de \
    --cc=heiko@sntech.de \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).