[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20140526074913.GD2650@dragon>
Date: Mon, 26 May 2014 15:49:15 +0800
From: Shawn Guo <shawn.guo@...escale.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
CC: Daniel Lezcano <daniel.lezcano@...aro.org>,
Olof Johansson <olof@...om.net>, Arnd Bergmann <arnd@...db.de>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-next@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
Cosmin Stoica <cosminstefan.stoica@...escale.com>,
Xiubo Li <Li.Xiubo@...escale.com>
Subject: Re: linux-next: manual merge of the clockevents tree with the
arm-soc tree
Hi Daniel,
On Mon, May 26, 2014 at 03:43:31PM +1000, Stephen Rothwell wrote:
> Hi Daniel,
>
> Today's linux-next merge of the clockevents tree got a conflict in
> arch/arm/boot/dts/vf610.dtsi between commit 0517fe6aa880 ("ARM: dts:
> vf610-twr: Add support for sdhc1") from the arm-soc tree and commit
> 07513e1330a9 ("ARM: dts: vf610: Add Freescale FlexTimer Module timer
> node") from the clockevents tree.
Next time, please leave the dts patches to go via arch tree, so that we
can save such conflicts.
Shawn
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists