From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: Current OMAP build failures
Date: Thu, 6 Jan 2011 17:10:19 +0000 [thread overview]
Message-ID: <20110106171019.GF1198@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <878vyyx8s4.fsf@ti.com>
On Thu, Jan 06, 2011 at 09:05:15AM -0800, Kevin Hilman wrote:
> Hi Russell,
>
> Russell King - ARM Linux <linux@arm.linux.org.uk> writes:
>
> > I've observed the following issues while building 2.6.37 + my devel
> > branch. I don't believe any of them to be due to anything in my tree,
> > so would be in 2.6.37 as well.
>
> What defconfig are you using for these builds?
I couldn't say offhand because they're built from configs created a while
back. I tend to just re-run the build with appropriate O= arguments to
test things.
I can send the defconfigs if it'd help.
next prev parent reply other threads:[~2011-01-06 17:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-06 11:03 Current OMAP build failures Russell King - ARM Linux
2011-01-06 12:11 ` Santosh Shilimkar
2011-01-06 17:05 ` Kevin Hilman
2011-01-06 17:10 ` Russell King - ARM Linux [this message]
2011-01-06 17:49 ` Tony Lindgren
2011-01-06 18:03 ` Russell King - ARM Linux
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=20110106171019.GF1198@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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).