[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220527103916.52768f74@canb.auug.org.au>
Date: Fri, 27 May 2022 10:39:16 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Olof Johansson <olof@...om.net>, Arnd Bergmann <arnd@...db.de>,
ARM <linux-arm-kernel@...ts.infradead.org>
Cc: Geert Uytterhoeven <geert@...ux-m68k.org>,
Laurent Vivier <laurent@...ier.eu>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Nick Hawkins <nick.hawkins@....com>
Subject: linux-next: manual merge of the arm-soc tree with Linus' tree
Hi all,
Today's linux-next merge of the arm-soc tree got a conflict in:
drivers/clocksource/Makefile
between commit:
c92e7ef16400 ("clocksource/drivers: Add a goldfish-timer clocksource")
from Linus' tree and commit:
5184f4bf151b ("clocksource/drivers/timer-gxp: Add HPE GXP Timer")
from the arm-soc 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 drivers/clocksource/Makefile
index 833cfb7a96c1,98017abf6c03..000000000000
--- a/drivers/clocksource/Makefile
+++ b/drivers/clocksource/Makefile
@@@ -85,4 -88,4 +85,5 @@@ obj-$(CONFIG_GX6605S_TIMER) += timer-g
obj-$(CONFIG_HYPERV_TIMER) += hyperv_timer.o
obj-$(CONFIG_MICROCHIP_PIT64B) += timer-microchip-pit64b.o
obj-$(CONFIG_MSC313E_TIMER) += timer-msc313e.o
+obj-$(CONFIG_GOLDFISH_TIMER) += timer-goldfish.o
+ obj-$(CONFIG_GXP_TIMER) += timer-gxp.o
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists