From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lrg@ti.com>
Subject: Re: [PATCH v2 00/10] Combining snd_soc_*_volsw/volsw_2r
Date: Wed, 5 Oct 2011 17:10:34 +0100 [thread overview]
Message-ID: <20111005161033.GA11528@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1317799768-15683-1-git-send-email-peter.ujfalusi@ti.com>
On Wed, Oct 05, 2011 at 10:29:18AM +0300, Peter Ujfalusi wrote:
> This series will combine the snd_soc_*_volsw, and snd_soc_*_volsw_2r callbacks.
Applied all, thanks.
prev parent reply other threads:[~2011-10-05 16:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-05 7:29 [PATCH v2 00/10] Combining snd_soc_*_volsw/volsw_2r Peter Ujfalusi
2011-10-05 7:29 ` [PATCH v2 01/10] ASoC: Consolidate use of controls with custom get/put function Peter Ujfalusi
2011-10-05 7:29 ` [PATCH v2 02/10] ASoC: twl6040: Simplify custom get_volsw callback Peter Ujfalusi
2011-10-05 7:29 ` [PATCH v2 03/10] ASoC: twl6040: Prepare for core put_volsw/volsw_2r merger Peter Ujfalusi
2011-10-05 7:29 ` [PATCH v2 04/10] ASoC: core: Change SOC_SINGLE/DOUBLE_VALUE representation Peter Ujfalusi
2011-10-05 7:29 ` [PATCH v2 05/10] ASoC: core: Combine snd_soc_info_volsw/info_volsw_2r functions Peter Ujfalusi
2011-10-05 7:29 ` [PATCH v2 06/10] ASoC: core: Combine snd_soc_get_volsw/get_volsw_2r functions Peter Ujfalusi
2011-10-05 7:29 ` [PATCH v2 07/10] ASoC: core: Combine snd_soc_put_volsw/put_volsw_2r functions Peter Ujfalusi
2011-10-05 7:29 ` [PATCH v2 08/10] ASoC: twl6040: Simply call snd_soc_put_volsw form the custom code Peter Ujfalusi
2011-10-05 7:29 ` [PATCH v2 09/10] ASoC: core: Remove snd_soc_put_volsw_2r definition Peter Ujfalusi
2011-10-05 7:29 ` [PATCH v2 10/10] ASoC: twl6040: Warn user in twl6040_put_volsw for error case Peter Ujfalusi
2011-10-05 16:10 ` 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=20111005161033.GA11528@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=lrg@ti.com \
--cc=peter.ujfalusi@ti.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