From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Koul, Vinod" <vinod.koul@intel.com>
Cc: alsa-devel@alsa-project.org,
Harsha Priya <priya.harsha@intel.com>,
akpm@linux-foundation.org, lrg@slimlogic.co.uk
Subject: Re: [PATCH] ASoC: mid-x86: Fix dependency on intel_sst driver
Date: Mon, 7 Feb 2011 11:26:41 +0000 [thread overview]
Message-ID: <20110207112640.GA10564@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1296986748-22614-1-git-send-email-vinod.koul@intel.com>
On Sun, Feb 06, 2011 at 03:35:48PM +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!
Applied, thanks.
prev parent reply other threads:[~2011-02-07 11:26 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
2011-02-07 11:26 ` Mark Brown [this message]
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=20110207112640.GA10564@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=akpm@linux-foundation.org \
--cc=alsa-devel@alsa-project.org \
--cc=lrg@slimlogic.co.uk \
--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).