All of lore.kernel.org
 help / color / mirror / Atom feed
From: jason@lakedaemon.net (Jason Cooper)
To: linux-arm-kernel@lists.infradead.org
Subject: Build failed for mvebu in linux-next due to duplicate commit for RTC
Date: Tue, 26 Feb 2013 13:05:19 -0500	[thread overview]
Message-ID: <20130226180519.GD23237@titan.lakedaemon.net> (raw)
In-Reply-To: <512CEFEA.4060301@free-electrons.com>

On Tue, Feb 26, 2013 at 06:24:58PM +0100, Gregory CLEMENT wrote:
> Hello,
> 
> when I tried to use the linux-next git tree (next-20130226), I
> encountered this error during build:
> 
> ERROR (duplicate_node_names): Duplicate node name /soc/rtc at 10300

Nice catch!

> I found it was because 2 version of the same patch have been submitted
> to linux-next,
> git log v3.8..HEAD --grep=RTC  arch/arm/boot/dts/armada-370-xp.dtsi
> 
> commit 25fe89035eb81ea8be7ebb98eba18a8da744d3a2
> Author: Gregory CLEMENT <gregory.clement@free-electrons.com>
> Date:   Wed Feb 20 13:15:47 2013 +1100
> 
>     arm: mvebu: add RTC support for Armada 370 and Armada XP
> 
>     The Armada 370 and Armada XP Socs have the same controller that the one
>     used in the orion platforms.  This patch updates the device tree for these
>     SoCs.
> 
>     Signed-off-by: Gregory CLEMENT <gregory.clement@free-electrons.com>
>     Acked-by: Andrew Lunn <andrew@lunn.ch>
>     Cc: Russell King <linux@arm.linux.org.uk>
>     Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> 
> commit f70a08ce13cdec674eae271a2e76554ff20bf5f3
> Author: Gregory CLEMENT <gregory.clement@free-electrons.com>
> Date:   Wed Dec 12 10:06:24 2012 +0100
> 
>     arm: mvebu: Add RTC support for Armada 370 and Armada XP
> 
>     The Armada 370 and Armada XP Socs have the same controller that the
>     one used in the orion platforms. This patch updates the device tree
>     for these SoCs.
> 
>     Signed-off-by: Gregory CLEMENT <gregory.clement@free-electrons.com>
>     Acked-by: Andrew Lunn <andrew@lunn.ch>
>     Tested-by: Florian Fainelli <florian@openwrt.org>
>     Acked-by: Arnd Bergmann <arnd@arndb.de>
>     Signed-off-by: Jason Cooper <jason@lakedaemon.net>
> 
> I think that the commit 25fe89 came through Andrew Morton and my
> second version f70a08ce came through Jason Cooper and then arm-soc.
> 
> First, what I have to do to fix this? The best solution should be to
> remove the commit 25fe890 as it is the less recent. How can we
> proceed ?

Is the diffstat different between the versions?

> Then I am sorry to not have figure out this before. I thought the
> automatic email I received from Andrew Morton where due to Jason that
> have been pushed the patch to Andrew Morton. I wasn't aware that
> Andrew Morton took care of the RTC subsystem a well.

At this point, it's moot which path was correct.  Whichever is easiest
to revert should be reverted.  Thankfully it's not C code causing a
build breakage.  The patch was just adding a devicetree node.

Arnd/Olof, what do you recommend here?

thx,

Jason.

  reply	other threads:[~2013-02-26 18:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-26 17:24 Build failed for mvebu in linux-next due to duplicate commit for RTC Gregory CLEMENT
2013-02-26 18:05 ` Jason Cooper [this message]
2013-02-26 18:09   ` Olof Johansson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130226180519.GD23237@titan.lakedaemon.net \
    --to=jason@lakedaemon.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.