[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20200317084441.1f59756d@canb.auug.org.au>
Date: Tue, 17 Mar 2020 08:44:41 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Shawn Guo <shawnguo@...nel.org>
Cc: Linux Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Yangtao Li <tiny.windzz@...il.com>,
Maxime Ripard <maxime@...no.tech>,
Anson Huang <Anson.Huang@....com>,
Geert Uytterhoeven <geert+renesas@...der.be>,
Li Yang <leoyang.li@....com>
Subject: linux-next: manual merge of the imx-mxs tree with Linus' tree
Hi all,
Today's linux-next merge of the imx-mxs tree got a conflict in:
arch/arm64/configs/defconfig
between commits:
4a453ccf87d5 ("arm64: defconfig: Enable CONFIG_SUN8I_THERMAL")
d5888c8e5586 ("arm64: defconfig: Replace ARCH_R8A7796 by ARCH_R8A77960")
from Linus' tree and commits:
34e46ed80df6 ("arm64: defconfig: add i.MX system controller thermal support")
63cccc8401c2 ("arm64: defconfig: Enable CONFIG_IMX8MM_THERMAL as module")
3fbd82f9af29 ("arm64: defconfig: run through savedefconfig for ordering")
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 4db223dbc549,0c110182497a..000000000000
--- a/arch/arm64/configs/defconfig
+++ b/arch/arm64/configs/defconfig
@@@ -452,7 -485,8 +485,9 @@@ CONFIG_THERMAL_GOV_POWER_ALLOCATOR=
CONFIG_CPU_THERMAL=y
CONFIG_THERMAL_EMULATION=y
CONFIG_QORIQ_THERMAL=m
+CONFIG_SUN8I_THERMAL=y
+ CONFIG_IMX_SC_THERMAL=m
+ CONFIG_IMX8MM_THERMAL=m
CONFIG_ROCKCHIP_THERMAL=m
CONFIG_RCAR_THERMAL=y
CONFIG_RCAR_GEN3_THERMAL=y
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists