From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: arm tree build failure
Date: Fri, 29 Jan 2010 23:45:01 +0000 [thread overview]
Message-ID: <20100129234501.GA31198@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20100129103837.02cc865f.sfr@canb.auug.org.au>
On Fri, Jan 29, 2010 at 10:38:37AM +1100, Stephen Rothwell wrote:
> Hi Russell,
>
> Yesterday's linux-next (next-20100128) build (arm versatile_defconfig)
> failed like this:
>
> arch/arm/mach-versatile/core.c: In function 'versatile_init':
> arch/arm/mach-versatile/core.c:838: error: 'i' undeclared (first use in this function)
>
> Looks like a bad merge (commit b7cdd38da36d61d0f42367057c9d04678644317a
> "Merge branch 'versatile' into devel").
Thanks for catching that, now fixed.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
next prev parent reply other threads:[~2010-01-29 23:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-28 23:38 linux-next: arm tree build failure Stephen Rothwell
2010-01-29 23:45 ` Russell King [this message]
2010-01-30 1:27 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2009-09-10 4:59 Stephen Rothwell
2009-09-14 8:20 ` Russell King
2009-04-14 7:48 Stephen Rothwell
2009-04-14 17:09 ` Russell King
2009-02-14 4:27 Stephen Rothwell
2009-02-16 9:23 ` Catalin Marinas
2008-09-18 18:09 Stephen Rothwell
2008-09-18 18:26 ` Eric Miao
2008-09-18 18:33 ` Eric Miao
2008-09-18 22:04 ` Russell King
2008-09-18 22:28 ` Eric Miao
2008-08-19 5:53 Stephen Rothwell
2008-08-19 11:16 ` Marek Vasut
2008-08-19 11:21 ` Takashi Iwai
2008-08-19 16:06 ` Russell King
2008-08-19 16:32 ` Takashi Iwai
2008-08-20 0:01 ` Stephen Rothwell
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=20100129234501.GA31198@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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.