From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Stephen Warren <swarren@nvidia.com>
Cc: alsa-devel@alsa-project.org, lrg@ti.com
Subject: Re: [PATCH] ASoC: Fix dapm_is_shared_kcontrol so everything isn't shared
Date: Fri, 27 May 2011 21:59:33 +0800 [thread overview]
Message-ID: <20110527135932.GA4240@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1306425453-20753-1-git-send-email-swarren@nvidia.com>
On Thu, May 26, 2011 at 09:57:33AM -0600, Stephen Warren wrote:
> Commit af46800 ("ASoC: Implement mux control sharing") introduced
> function dapm_is_shared_kcontrol.
>
> When this function returns true, the naming of DAPM controls is derived
> from the kcontrol_new. Otherwise, the name comes from the widget (and
> possibly a widget's naming prefix).
Applied, thanks.
next prev parent reply other threads:[~2011-05-27 13:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-26 15:57 [PATCH] ASoC: Fix dapm_is_shared_kcontrol so everything isn't shared Stephen Warren
2011-05-26 18:02 ` Jarkko Nikula
2011-05-27 9:19 ` Liam Girdwood
2011-05-27 13:59 ` Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-05-24 23:12 Stephen Warren
2011-05-25 7:01 ` Jarkko Nikula
2011-05-25 14:52 ` Jarkko Nikula
2011-05-25 15:24 ` Stephen Warren
2011-05-26 6:57 ` Jarkko Nikula
2011-05-26 15:38 ` Stephen Warren
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=20110527135932.GA4240@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=lrg@ti.com \
--cc=swarren@nvidia.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