From: Anand Gadiyar <gadiyar@ti.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: linux-next@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: RE: linux-next-20100201 - OMAP2+ defconfig broken withCONFIG_DEBUG_LL
Date: Tue, 1 Feb 2011 14:55:01 +0530 [thread overview]
Message-ID: <65ee8ac703eaa856dff7957d7966b627@mail.gmail.com> (raw)
In-Reply-To: <20110201092238.GA31015@n2100.arm.linux.org.uk>
Russell King - ARM Linux wrote:
> On Tue, Feb 01, 2011 at 11:09:52AM +0530, 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.
>
> No need to bisect. Tony knows about it. It's the OMAP debug code using
> what was a macro in assembly, which becomes a C function with the
dynamic
> P2V patches.
>
Okay, thanks!
- Anand
next prev parent reply other threads:[~2011-02-01 9:25 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 ` Anand Gadiyar [this message]
2011-02-01 9:23 ` Anand Gadiyar
2011-02-01 9:26 ` Santosh Shilimkar
2011-02-04 19:59 ` Tony Lindgren
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=65ee8ac703eaa856dff7957d7966b627@mail.gmail.com \
--to=gadiyar@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
/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).