From: Lars-Peter Clausen <lars@metafoo.de>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, linaro-kernel@lists.linaro.org,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@linaro.org>
Subject: Re: [PATCH 1/2] ASoC: ad73311: Add DAPM support
Date: Thu, 08 Aug 2013 13:55:59 +0200 [thread overview]
Message-ID: <5203874F.8050106@metafoo.de> (raw)
In-Reply-To: <1375894913-8608-1-git-send-email-broonie@kernel.org>
On 08/07/2013 07:01 PM, Mark Brown wrote:
> From: Mark Brown <broonie@linaro.org>
>
> This makes it possible to hook up other devices in boards and is required
> by removal of support for non-DAPM CODECs in the core.
>
> Signed-off-by: Mark Brown <broonie@linaro.org>
Acked-by: Lars-Peter Clausen <lars@metafoo.de>
Thanks.
prev parent reply other threads:[~2013-08-08 11:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-07 17:01 [PATCH 1/2] ASoC: ad73311: Add DAPM support Mark Brown
2013-08-07 17:01 ` [PATCH 2/2] ASoC: ad73311: Add to list of of Analog Devices supported CODECs Mark Brown
2013-08-08 11:56 ` Lars-Peter Clausen
2013-08-08 11:55 ` Lars-Peter Clausen [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=5203874F.8050106@metafoo.de \
--to=lars@metafoo.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=broonie@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linaro-kernel@lists.linaro.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).