[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <m2inpc192q.fsf@baylibre.com>
Date: Wed, 18 Jan 2017 11:06:53 -0800
From: Kevin Hilman <khilman@...libre.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Carlo Caione <carlo@...one.org>, Olof Johansson <olof@...om.net>,
Arnd Bergmann <arnd@...db.de>,
ARM <linux-arm-kernel@...ts.infradead.org>,
linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
Neil Armstrong <narmstrong@...libre.com>,
Martin Blumenstingl <martin.blumenstingl@...glemail.com>
Subject: Re: linux-next: manual merge of the amlogic tree with the arm-soc tree
Stephen Rothwell <sfr@...b.auug.org.au> writes:
> Hi all,
>
> Today's linux-next merge of the amlogic tree got a conflict in:
>
> arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi
>
> between commit:
>
> f7bcd4b6f698 ("ARM64: dts: meson-gxbb-odroidc2: Disable SCPI DVFS")
>
> from the arm-soc tree and commit:
>
> 47961f1353b8 ("ARM64: dts: meson-gx: move the SCPI and SRAM nodes to meson-gx")
>
> from the amlogic tree.
The latter has been dropped from the amlogic pending some ongoing
discussion, but I forgot to push an updated for-next. That's remedied
now.
Kevin
Powered by blists - more mailing lists