From: Russell King <rmk@arm•linux.org.uk>
To: Alan Cox <alan@lxorguk•ukuu.org.uk>,
Grant Likely <grant.likely@secretlab•ca>
Cc: linux-next@vger•kernel.org
Subject: Re: Breakage from ARM when building x86
Date: Tue, 14 Feb 2012 16:53:05 +0000 [thread overview]
Message-ID: <20120214165305.GA6362@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20120214164453.003d9777@pyramind.ukuu.org.uk>
On Tue, Feb 14, 2012 at 04:44:53PM +0000, Alan Cox wrote:
> Either this needs the headers fixing or should be protected by an ARM
> config, not sure which
At a guess, this is from linux-next ?
> drivers/mfd/twl-core.c: In function ‘twl_probe’:
> drivers/mfd/twl-core.c:1218:2: error: implicit declaration of function
> ‘irq_alloc_descs’ [-Werror=implicit-function-declaration]
> drivers/mfd/twl-core.c:1226:2: error: implicit declaration of function
> ‘irq_domain_add_legacy’ [-Werror=implicit-function-declaration]
> drivers/mfd/twl-core.c:1227:11: error: ‘irq_domain_simple_ops’ undeclared
> (first use in this function) drivers/mfd/twl-core.c:1227:11: note: each
> undeclared identifier is reported only once for each function it appears
> in cc1: some warnings being treated as errors
This has nothing to do with me ;) You're not the first to report it today.
I'm told by OMAP people that TWL gets used on x86 as well so it can't be
restricted to just ARM.
This is probably due to the irq domain stuff coming out of Grant's tree.
So no, really not anything to do with ARM.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
next prev parent reply other threads:[~2012-02-14 16:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-14 16:44 Breakage from ARM when building x86 Alan Cox
2012-02-14 16:53 ` Russell King [this message]
2012-02-14 17:09 ` Grant Likely
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=20120214165305.GA6362@flint.arm.linux.org.uk \
--to=rmk@arm$(echo .)linux.org.uk \
--cc=alan@lxorguk$(echo .)ukuu.org.uk \
--cc=grant.likely@secretlab$(echo .)ca \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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