[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20141208120619.68287b54@canb.auug.org.au>
Date: Mon, 8 Dec 2014 12:06:19 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Stephen Warren <swarren@...dotorg.org>,
Olof Johansson <olof@...om.net>, Arnd Bergmann <arnd@...db.de>,
<linux-arm-kernel@...ts.infradead.org>
Cc: linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
Rafał Miłecki <zajec5@...il.com>,
Hauke Mehrtens <hauke@...ke-m.de>,
Matthias Klein <matthias.klein@...ux.com>,
Lee Jones <lee.jones@...aro.org>
Subject: linux-next: manual merge of the bcm2835 tree with the arm-soc tree
Hi Stephen,
Today's linux-next merge of the bcm2835 tree got a conflict in
arch/arm/boot/dts/Makefile between commit 302a5ef29d49 ("ARM: BCM5301X:
Add DT for Netgear R6300 V2") from the arm-soc tree and commit
6298ed17a404 ("ARM: bcm2835: Add device tree for Raspberry Pi model
B+") from the bcm2835 tree.
I fixed it up (the bcm2835 tree patch is also in the arm-soc tree as
commit ba2a1d6959ac ("ARM: bcm2835: Add device tree for Raspberry Pi
model B+"), so I just used the arm-soc version) and can carry the fix
as necessary (no action is required).
--
Cheers,
Stephen Rothwell sfr@...b.auug.org.au
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists