From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Rajeev Kumar <rajeev-dlh.kumar@st.com>
Cc: tiwai@suse.de, alsa-devel@alsa-project.org, lrg@slimlogic.co.uk
Subject: Re: [PATCH V2 4/5] sound: asoc: Adding Kconfig and Makefile to support SPEAr13XX ASoC driver
Date: Wed, 30 Mar 2011 08:33:02 +0900 [thread overview]
Message-ID: <20110329233300.GM30482@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1301397423-4693-5-git-send-email-rajeev-dlh.kumar@st.com>
On Tue, Mar 29, 2011 at 04:47:02PM +0530, Rajeev Kumar wrote:
> +++ b/sound/soc/spear/Makefile
> @@ -0,0 +1,6 @@
> +# SPEAR Platform Support
> +obj-$(CONFIG_SND_SOC_SPEAR) += spear13xx-pcm.o
> +obj-$(CONFIG_SND_SOC_SPEAR_I2S) += spear13xx-i2s.o
> +
> +# SPEAR Machine Support
> +obj-$(CONFIG_SND_SOC_SPEAR_EVM) += evb_sta529.o
As previously mentioned you should give all the modules snd-soc-
prefixes to their names.
next prev parent reply other threads:[~2011-03-29 23:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-29 11:16 [PATCH V2 0/5] Adding ASoC drivers for SPEAr13XX platform Rajeev Kumar
2011-03-29 11:16 ` [PATCH V2 1/5] sound: asoc: Adding support for STA529 Audio Codec Rajeev Kumar
2011-03-29 11:17 ` [PATCH V2 2/5] sound: asoc: Adding support for SPEAr13XX ASoC platform driver Rajeev Kumar
2011-03-29 11:17 ` [PATCH V2 3/5] sound: asoc: Adding support for SPEAr13XX ASoC machine driver Rajeev Kumar
2011-03-29 11:17 ` [PATCH V2 4/5] sound: asoc: Adding Kconfig and Makefile to support SPEAr13XX ASoC driver Rajeev Kumar
2011-03-29 11:17 ` [PATCH V2 5/5] sound: asoc: Adding support for SPEAr13XX in soc Rajeev Kumar
2011-03-29 23:33 ` Mark Brown [this message]
2011-03-30 4:22 ` [PATCH V2 4/5] sound: asoc: Adding Kconfig and Makefile to support SPEAr13XX ASoC driver rajeev
2011-03-29 23:32 ` [PATCH V2 3/5] sound: asoc: Adding support for SPEAr13XX ASoC machine driver Mark Brown
2011-03-30 4:55 ` rajeev
2011-04-08 5:16 ` rajeev
2011-03-29 23:27 ` [PATCH V2 1/5] sound: asoc: Adding support for STA529 Audio Codec Mark Brown
2011-04-08 5:39 ` rajeev
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=20110329233300.GM30482@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=lrg@slimlogic.co.uk \
--cc=rajeev-dlh.kumar@st.com \
--cc=tiwai@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.