[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20190506104357.18e10955@canb.auug.org.au>
Date: Mon, 6 May 2019 10:43:57 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Shawn Guo <shawnguo@...nel.org>, Olof Johansson <olof@...om.net>,
Arnd Bergmann <arnd@...db.de>,
ARM <linux-arm-kernel@...ts.infradead.org>
Cc: Linux Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Dinh Nguyen <dinguyen@...nel.org>,
Fabio Estevam <festevam@...il.com>
Subject: linux-next: manual merge of the imx-mxs tree with the arm-soc tree
Hi all,
Today's linux-next merge of the imx-mxs tree got a conflict in:
arch/arm64/configs/defconfig
between commit:
7b0d021fbe41 ("arm64: defconfig: enable PCIE_ALTERA")
from the arm-soc tree and commit:
a9aa2a812255 ("arm64: defconfig: Enable CONFIG_SPI_IMX")
from the imx-mxs 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/configs/defconfig
index 5392c12ef3b7,979a95c915b6..000000000000
--- a/arch/arm64/configs/defconfig
+++ b/arch/arm64/configs/defconfig
@@@ -357,7 -365,7 +358,8 @@@ CONFIG_SPI=
CONFIG_SPI_ARMADA_3700=y
CONFIG_SPI_BCM2835=m
CONFIG_SPI_BCM2835AUX=m
+ CONFIG_SPI_IMX=m
+CONFIG_SPI_NXP_FLEXSPI=y
CONFIG_SPI_MESON_SPICC=m
CONFIG_SPI_MESON_SPIFC=m
CONFIG_SPI_ORION=y
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists