From: Randy Dunlap <rdunlap@xenotime.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Samuel Ortiz <sameo@linux.intel.com>,
Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: [PATCH -next] mfd: fix arizona-irq.c build by selecting REGMAP_IRQ
Date: Mon, 23 Jul 2012 10:32:58 -0700 [thread overview]
Message-ID: <500D8ACA.4020501@xenotime.net> (raw)
In-Reply-To: <20120723164036.52bc93caafcd165fc16f0284@canb.auug.org.au>
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(+)
--- linux-next-20120723.orig/drivers/mfd/Kconfig
+++ linux-next-20120723/drivers/mfd/Kconfig
@@ -523,6 +523,7 @@ config MFD_SEC_CORE
config MFD_ARIZONA
select REGMAP
+ select REGMAP_IRQ
bool
config MFD_ARIZONA_I2C
next prev parent reply other threads:[~2012-07-23 17:34 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 ` Randy Dunlap [this message]
2012-07-23 17:39 ` [PATCH -next] mfd: fix arizona-irq.c build by selecting REGMAP_IRQ Mark Brown
2012-07-24 22:56 ` Samuel Ortiz
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=500D8ACA.4020501@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sameo@linux.intel.com \
--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).