From: Liam Girdwood <lrg@slimlogic.co.uk>
To: "Koul, Vinod" <vinod.koul@intel.com>
Cc: Harsha Priya <priya.harsha@intel.com>,
alsa-devel@alsa-project.org, broonie@opensource.wolfsonmicro.com,
akpm@linux-foundation.org
Subject: Re: [PATCH] ASoC: mid-x86: Fix dependency on intel_sst driver
Date: Sun, 06 Feb 2011 14:42:01 +0000 [thread overview]
Message-ID: <1297003321.3315.163.camel@odin> (raw)
In-Reply-To: <1296986748-22614-1-git-send-email-vinod.koul@intel.com>
On Sun, 2011-02-06 at 15:35 +0530, Koul, Vinod wrote:
> From: Vinod Koul <vinod.koul@intel.com>
>
> Enabling medfield asoc driver causes compliation error when intel_sst
> is not selected
> ERROR: "register_sst_card" [sound/soc/mid-x86/snd-soc-sst-platform.ko]
> undefined!
>
> This patch puts proper dependency to elimate build error
>
> Signed-off-by: Vinod Koul <vinod.koul@intel.com>
> Signed-off-by: Harsha Priya <priya.harsha@intel.com>
> Reported-by: Andrew Morton <akpm@linux-foundation.org>
> ---
> sound/soc/mid-x86/Kconfig | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/sound/soc/mid-x86/Kconfig b/sound/soc/mid-x86/Kconfig
> index 1ad7538..2935042 100644
> --- a/sound/soc/mid-x86/Kconfig
> +++ b/sound/soc/mid-x86/Kconfig
> @@ -1,6 +1,7 @@
> config SND_MFLD_MACHINE
> tristate "SOC Machine Audio driver for Intel Medfield MID platform"
> depends on INTEL_SCU_IPC
> + depends on SND_INTEL_SST
> select SND_SOC_SN95031
> select SND_SST_PLATFORM
> help
> @@ -11,4 +12,3 @@ config SND_MFLD_MACHINE
>
> config SND_SST_PLATFORM
> tristate
> - depends on SND_INTEL_SST
Acked-by: liam Girdwood <lrg@slimlogic.co.uk>
--
Freelance Developer, SlimLogic Ltd
ASoC and Voltage Regulator Maintainer.
http://www.slimlogic.co.uk
next prev parent reply other threads:[~2011-02-06 14:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-06 10:05 [PATCH] ASoC: mid-x86: Fix dependency on intel_sst driver Koul, Vinod
2011-02-06 14:42 ` Liam Girdwood [this message]
2011-02-07 11:26 ` Mark Brown
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=1297003321.3315.163.camel@odin \
--to=lrg@slimlogic.co.uk \
--cc=akpm@linux-foundation.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=priya.harsha@intel.com \
--cc=vinod.koul@intel.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).