Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Thu, 24 Sep 2020 11:57:31 +1000
From:   Stephen Rothwell <sfr@canb.auug.org.au>
To:     Bjorn Helgaas <bhelgaas@google.com>,
        Shawn Guo <shawnguo@kernel.org>
Cc:     Wasim Khan <wasim.khan@nxp.com>,
        Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
        Xiaowei Bao <xiaowei.bao@nxp.com>,
        Linux Next Mailing List <linux-next@vger.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: linux-next: manual merge of the pci tree with the imx-mxs tree
Message-ID: <20200924115731.194ecd6f@canb.auug.org.au>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="Sig_/K8bMVqusV0Gxwgrjehxi5oo";
 protocol="application/pgp-signature"; micalg=pgp-sha256
Precedence: bulk

--Sig_/K8bMVqusV0Gxwgrjehxi5oo
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Hi all,

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

  arch/arm64/boot/dts/freescale/fsl-ls1088a.dtsi

between commit:

  f7d48ffcfc6e ("arm64: dts: layerscape: Add label to pcie nodes")

from the imx-mxs tree and commit:

  c9443b6500ff ("arm64: dts: layerscape: Add PCIe EP node for ls1088a")

from the pci 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.

--=20
Cheers,
Stephen Rothwell

diff --cc arch/arm64/boot/dts/freescale/fsl-ls1088a.dtsi
index ff5805206a28,f21dd143ab6d..000000000000
--- a/arch/arm64/boot/dts/freescale/fsl-ls1088a.dtsi
+++ b/arch/arm64/boot/dts/freescale/fsl-ls1088a.dtsi
@@@ -517,7 -499,18 +517,18 @@@
  			status =3D "disabled";
  		};
 =20
+ 		pcie-ep@3400000 {
+ 			compatible =3D "fsl,ls1088a-pcie-ep","fsl,ls-pcie-ep";
+ 			reg =3D <0x00 0x03400000 0x0 0x00100000
+ 			       0x20 0x00000000 0x8 0x00000000>;
+ 			reg-names =3D "regs", "addr_space";
+ 			num-ib-windows =3D <24>;
+ 			num-ob-windows =3D <128>;
+ 			max-functions =3D /bits/ 8 <2>;
+ 			status =3D "disabled";
+ 		};
+=20
 -		pcie@3500000 {
 +		pcie2: pcie@3500000 {
  			compatible =3D "fsl,ls1088a-pcie";
  			reg =3D <0x00 0x03500000 0x0 0x00100000   /* controller registers */
  			       0x28 0x00000000 0x0 0x00002000>; /* configuration space */
@@@ -543,7 -536,17 +554,17 @@@
  			status =3D "disabled";
  		};
 =20
+ 		pcie-ep@3500000 {
+ 			compatible =3D "fsl,ls1088a-pcie-ep","fsl,ls-pcie-ep";
+ 			reg =3D <0x00 0x03500000 0x0 0x00100000
+ 			       0x28 0x00000000 0x8 0x00000000>;
+ 			reg-names =3D "regs", "addr_space";
+ 			num-ib-windows =3D <6>;
+ 			num-ob-windows =3D <8>;
+ 			status =3D "disabled";
+ 		};
+=20
 -		pcie@3600000 {
 +		pcie3: pcie@3600000 {
  			compatible =3D "fsl,ls1088a-pcie";
  			reg =3D <0x00 0x03600000 0x0 0x00100000   /* controller registers */
  			       0x30 0x00000000 0x0 0x00002000>; /* configuration space */

--Sig_/K8bMVqusV0Gxwgrjehxi5oo
Content-Type: application/pgp-signature
Content-Description: OpenPGP digital signature

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEENIC96giZ81tWdLgKAVBC80lX0GwFAl9r/QsACgkQAVBC80lX
0GxA/Qf/XpS8U+zhGNJ/aAQZySZYBtqoe0Ii2GP62XZjOp9VvwlGQACEgTd9uqAt
TwyioJbYis7/WondxLEz29HhGvbPXV8mEmPGzmWNdPyi16SrTTROeltwiamhXf3a
MCRi432Rh81xZmjfnKNUCnJq6Kg4J4XZS9/lO1ATT4YzkCYDlzRtfyMRF+s0jgEN
ro9Itvuy1F7QOERgy952mLSKm9jw1MSkIuMUnkcQ8lO1AFoVM6ZiTbcSWa4WEyuo
isLXLW5ZzfH8ItZUxC+XnoCuK66zo34O4aAUE351qf0/nCcSMBaBbSU+huFpnfZB
i56mDukhUAT/SRUkbRaezCog6KbaLA==
=Y+El
-----END PGP SIGNATURE-----

--Sig_/K8bMVqusV0Gxwgrjehxi5oo--