From: Rob Herring <robherring2@gmail.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Axel Lin <axel.lin@gmail.com>,
Marc Zyngier <marc.zyngier@arm.com>,
linux-kernel@vger.kernel.org,
"Stephen Rothwell sfr"@canb.auug.org.au,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [linux-next 20111025] build failure with make u8500_defconfig
Date: Fri, 28 Oct 2011 16:22:45 -0500 [thread overview]
Message-ID: <4EAB1D25.9060002@gmail.com> (raw)
In-Reply-To: <CACRpkda7Q4q5YoWHbvC-gkcE99h0nUr3QhFT+GGuLGA4=V9gqg@mail.gmail.com>
On 10/28/2011 02:32 PM, Linus Walleij wrote:
> On Thu, Oct 27, 2011 at 5:11 AM, Axel Lin <axel.lin@gmail.com> wrote:
>
>> I got below build error by "make u8500_defconfig" on linux-next 20111025.
>>
>> CC arch/arm/common/gic.o
>> arch/arm/common/gic.c: In function 'gic_dist_init':
>> arch/arm/common/gic.c:290: error: 'irq_start' undeclared (first use in this function)
>> arch/arm/common/gic.c:290: error: (Each undeclared identifier is reported only once
>> arch/arm/common/gic.c:290: error: for each function it appears in.)
>> arch/arm/common/gic.c:296: error: 'struct gic_chip_data' has no member named 'irq_offset'
>> arch/arm/common/gic.c: In function 'gic_init':
>> arch/arm/common/gic.c:620: error: 'THIS_MODULE' undeclared (first use in this function)
>> make[1]: *** [arch/arm/common/gic.o] Error 1
>> make: *** [arch/arm/common] Error 2
>
> Hm I don't get it, the lines in the compile error seems to come from the
> "ARM: gic: consolidate PPI handling" patch, so Marc if this is my
> fault can you help me out in advicing me on how to fix it up properly?
>
It's a known issue and will get fixed when Arnd pulls my updated branch
for GIC DT support.
Rob
prev parent reply other threads:[~2011-10-28 21:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-27 3:11 [linux-next 20111025] build failure with make u8500_defconfig Axel Lin
2011-10-28 19:32 ` Linus Walleij
2011-10-28 21:22 ` Rob Herring [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=4EAB1D25.9060002@gmail.com \
--to=robherring2@gmail.com \
--cc="Stephen Rothwell sfr"@canb.auug.org.au \
--cc=arnd@arndb.de \
--cc=axel.lin@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.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).