From: "Shilimkar, Santosh" <santosh.shilimkar@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: Randconfig module build error with OMAP4_ERRATA_I688
Date: Thu, 1 Mar 2012 14:39:36 +0530 [thread overview]
Message-ID: <CAMQu2gxg_57AVW+MT_Sgi+gr2OUge-YPdSUxoG+z-zQth=4-UA@mail.gmail.com> (raw)
In-Reply-To: <20120229173719.GN18901@atomide.com>
On Wed, Feb 29, 2012 at 11:07 PM, Tony Lindgren <tony@atomide.com> wrote:
> Hi Santosh,
>
> Looks like OMAP4_ERRATA_I688 still has one more issue:
> Modules won't build at least with the attached randconfig
> generated file.
>
> Can you please take a look at how to deal with it?
>
> Maybe omap_bus_sync should be an inline function with some
> wrapper for the sleep44xx.S to call?
>
> I already posted a fix for the GPMC related error with the
> same .config file.
>
This one builds for me against 'Linux 3.3-rc5,
Ofocurse I got below error with the attached .config which
I bypassed to see the Errata build failure.
arch/arm/mach-omap2/built-in.o: In function `n8x0_mmc_callback':
linux-2.6/arch/arm/mach-omap2/board-n8x0.c:374: undefined reference to
`omap_mmc_notify_cover_event'
make: *** [.tmp_vmlinux1] Error 1
I build this with below toolchain...
$arm-none-linux-gnueabi-gcc --version
arm-none-linux-gnueabi-gcc (Sourcery G++ Lite 2011.03-41) 4.5.2
Copyright (C) 2010 Free Software Foundation, Inc.
Am I missing anything ?
Regards
Santosh
next prev parent reply other threads:[~2012-03-01 9:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 17:37 Randconfig module build error with OMAP4_ERRATA_I688 Tony Lindgren
2012-03-01 9:09 ` Shilimkar, Santosh [this message]
2012-03-01 16:25 ` Tony Lindgren
2012-03-02 11:46 ` Shilimkar, Santosh
2012-03-02 17:38 ` 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='CAMQu2gxg_57AVW+MT_Sgi+gr2OUge-YPdSUxoG+z-zQth=4-UA@mail.gmail.com' \
--to=santosh.shilimkar@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.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).