From: Randy Dunlap <randy.dunlap@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Zeng Zhaoming <zhaoming.zeng@freescale.com>
Cc: alsa-devel@alsa-project.org,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-next@vger.kernel.org, Liam@alsa-project.org,
Girdwood <lrg@slimlogic.co.uk>
Subject: [PATCH -next] soc: sgtl5000 uses regulator interfaces
Date: Fri, 4 Mar 2011 17:33:57 -0800 [thread overview]
Message-ID: <20110304173357.23d36116.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20110304180027.20deb6c4.sfr@canb.auug.org.au>
From: Randy Dunlap <randy.dunlap@oracle.com>
sgtl5000 uses regulator interfaces, so make selecting it depend
on REGULATOR.
sgtl5000.c:(.text+0x4ae33): undefined reference to `regulator_unregister'
sgtl5000.c:(.text+0x4af41): undefined reference to `rdev_get_drvdata'
sgtl5000.c:(.text+0x4b191): undefined reference to `regulator_register'
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Zeng Zhaoming <zhaoming.zeng@freescale.com>
---
sound/soc/codecs/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- linux-next-20110304.orig/sound/soc/codecs/Kconfig
+++ linux-next-20110304/sound/soc/codecs/Kconfig
@@ -33,7 +33,7 @@ config SND_SOC_ALL_CODECS
select SND_SOC_MAX98088 if I2C
select SND_SOC_MAX9877 if I2C
select SND_SOC_PCM3008
- select SND_SOC_SGTL5000 if I2C
+ select SND_SOC_SGTL5000 if I2C && REGULATOR
select SND_SOC_SN95031 if INTEL_SCU_IPC
select SND_SOC_SPDIF
select SND_SOC_SSM2602 if I2C
next parent reply other threads:[~2011-03-05 1:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110304180027.20deb6c4.sfr@canb.auug.org.au>
2011-03-05 1:33 ` Randy Dunlap [this message]
2011-03-05 11:29 ` [PATCH -next] soc: sgtl5000 uses regulator interfaces Mark Brown
2011-03-05 12:41 ` Zeng Zhaoming
2011-03-15 15:41 ` 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=20110304173357.23d36116.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=Liam@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=sfr@canb.auug.org.au \
--cc=zhaoming.zeng@freescale.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).