From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: arch/arm broken in next
Date: Sun, 28 Feb 2010 11:34:44 +0100 [thread overview]
Message-ID: <20100228103444.GC13987@pengutronix.de> (raw)
In-Reply-To: <20100228101239.63de9eb6.sfr@canb.auug.org.au>
Hi Stephen,
On Sun, Feb 28, 2010 at 10:12:39AM +1100, Stephen Rothwell wrote:
> On Sat, 27 Feb 2010 21:33:45 +0100 Uwe Kleine-K?nig <u.kleine-koenig@pengutronix.de> wrote:
> >
> > since
> >
> > 40464e5 (Merge remote branch 'samsung/next-samsung')
> >
> > next is broken for arch/arm. Our autobuilders fail with:
> >
> > arch/arm/Kconfig:920: file 'arch/arm/mach-lh7a40x/Kconfig' is already sourced from 'arch/arm/Kconfig'
> >
> > Both parents of 40464e5 only include the above file once.
>
> Yeah, sorry about that.
No problem, thanks to you for doing the work to maintain next.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-K?nig |
Industrial Linux Solutions | http://www.pengutronix.de/ |
prev parent reply other threads:[~2010-02-28 10:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-27 20:33 arch/arm broken in next Uwe Kleine-König
2010-02-27 23:12 ` Stephen Rothwell
2010-02-28 10:34 ` Uwe Kleine-König [this message]
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=20100228103444.GC13987@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).