From: Tony Lindgren <tony@atomide.com>
To: Santosh Shilimkar <santosh.shilimkar@ti.com>
Cc: Anand Gadiyar <gadiyar@ti.com>,
linux-arm-kernel@lists.infradead.org, linux-next@vger.kernel.org,
Russell King - ARM Linux <linux@arm.linux.org.uk>
Subject: Re: linux-next-20100201 - OMAP2+ defconfig broken with CONFIG_DEBUG_LL
Date: Fri, 4 Feb 2011 11:59:38 -0800 [thread overview]
Message-ID: <20110204195938.GA3322@atomide.com> (raw)
In-Reply-To: <7f99b6fa52967d67bf45d4e8aa7db1e8@mail.gmail.com>
* Santosh Shilimkar <santosh.shilimkar@ti.com> [110201 01:25]:
> > -----Original Message-----
> > From: linux-arm-kernel-bounces@lists.infradead.org [mailto:linux-
> > arm-kernel-bounces@lists.infradead.org] On Behalf Of Anand Gadiyar
> > Sent: Tuesday, February 01, 2011 2:54 PM
> > To: linux-arm-kernel@lists.infradead.org; linux-
> > next@vger.kernel.org; Russell King - ARM Linux
> > Subject: RE: linux-next-20100201 - OMAP2+ defconfig broken with
> > CONFIG_DEBUG_LL
> >
> > Gadiyar, Anand wrote:
> > > Hi all,
> > >
> > > I tried to build linux-next as of 20100201 with
> > > omap2plus_defconfig. In addition
> > > I turned on CONFIG_DEBUG_LL and hit the following error.
Posted a fix for that yesterday. Will upload it into Russell's
patch system for the p2v branch.
Tony
prev parent reply other threads:[~2011-02-04 20:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-01 5:39 linux-next-20100201 - OMAP2+ defconfig broken with CONFIG_DEBUG_LL Gadiyar, Anand
2011-02-01 9:22 ` Russell King - ARM Linux
2011-02-01 9:25 ` linux-next-20100201 - OMAP2+ defconfig broken withCONFIG_DEBUG_LL Anand Gadiyar
2011-02-01 9:23 ` linux-next-20100201 - OMAP2+ defconfig broken with CONFIG_DEBUG_LL Anand Gadiyar
2011-02-01 9:26 ` Santosh Shilimkar
2011-02-04 19:59 ` Tony Lindgren [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=20110204195938.GA3322@atomide.com \
--to=tony@atomide.com \
--cc=gadiyar@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=santosh.shilimkar@ti.com \
/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).