From: Samuel Ortiz <sameo@linux.intel.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: [PATCH -next] mfd: fix arizona-irq.c build by selecting REGMAP_IRQ
Date: Wed, 25 Jul 2012 00:56:19 +0200 [thread overview]
Message-ID: <20120724225619.GE11304@sortiz-mobl> (raw)
In-Reply-To: <500D8ACA.4020501@xenotime.net>
Hi Randy,
On Mon, Jul 23, 2012 at 10:32:58AM -0700, Randy Dunlap wrote:
> From: Randy Dunlap <rdunlap@xenotime.net>
>
> arizona-irq.c uses functions that are only available when
> CONFIG_REGMAP_IRQ is enabled, so select that symbol for
> arizona builds.
>
> Fixes these build errors:
>
> arizona-irq.c:(.text+0xb2d47): undefined reference to `regmap_irq_get_virq'
> (.text+0xb2fe3): undefined reference to `regmap_add_irq_chip'
> (.text+0xb3173): undefined reference to `regmap_del_irq_chip'
>
> Signed-off-by: Randy Dunlap <rdunlap@xenotime.net>
> Cc: Samuel Ortiz <sameo@linux.intel.com>
> Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>
> ---
> drivers/mfd/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
Applied, thanks.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
next prev parent reply other threads:[~2012-07-24 22:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-23 6:40 linux-next: Tree for July 23 Stephen Rothwell
2012-07-23 17:32 ` [PATCH -next] mfd: fix arizona-irq.c build by selecting REGMAP_IRQ Randy Dunlap
2012-07-23 17:39 ` Mark Brown
2012-07-24 22:56 ` Samuel Ortiz [this message]
2012-07-23 17:46 ` [PATCH -next] watchdog: fix watchdog-test.c build warning Randy Dunlap
2012-07-23 23:58 ` [PATCH -next] pstore: fix printk format warning Randy Dunlap
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=20120724225619.GE11304@sortiz-mobl \
--to=sameo@linux.intel.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=sfr@canb.auug.org.au \
/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).