From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Anuj Aggarwal <anuj.aggarwal@ti.com>
Cc: alsa-devel@alsa-project.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH 1/1] ASoC: AM3517: ASoC driver not getting compiled
Date: Fri, 29 Jan 2010 14:03:38 +0000 [thread overview]
Message-ID: <20100129140337.GD4768@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <1264760362-25465-1-git-send-email-anuj.aggarwal@ti.com>
On Fri, Jan 29, 2010 at 03:49:22PM +0530, Anuj Aggarwal wrote:
> Commit 761c9d45 (ASoC: Fix build of OMAP sound drivers) changes
> CONFIG_MACH_OMAP3517EVM -> CONFIG_SND_OMAP_SOC_OMAP3517EVM in the
> Makefile. Whereas the config option defined in Kconfig is
> SND_OMAP_SOC_AM3517EVM. Because of this, ASoC driver for AM3517
> was not getting compiled.
>
> Signed-off-by: Anuj Aggarwal <anuj.aggarwal@ti.com>
Applied, thanks.
prev parent reply other threads:[~2010-01-29 14:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-29 10:19 [PATCH 1/1] ASoC: AM3517: ASoC driver not getting compiled Anuj Aggarwal
2010-01-29 14:03 ` 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=20100129140337.GD4768@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=anuj.aggarwal@ti.com \
--cc=linux-omap@vger.kernel.org \
/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).