From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Liam Girdwood <lrg@slimlogic.co.uk>
Cc: alsa-devel@alsa-project.org
Subject: Re: UCM updates and fixes
Date: Wed, 22 Dec 2010 00:03:40 +0000 [thread overview]
Message-ID: <20101222000339.GD10081@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1292969520-18047-1-git-send-email-lrg@slimlogic.co.uk>
On Tue, Dec 21, 2010 at 10:11:49PM +0000, Liam Girdwood wrote:
> This fixes the remaining issues I can currently see in the alsa-lib
> ucm branch. It also includes a patch to execute commands, although I
> dont know if this is what you had in mind for exec.
All looks good to me.
next prev parent reply other threads:[~2010-12-22 0:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-21 22:11 UCM updates and fixes Liam Girdwood
2010-12-21 22:11 ` [PATCH 01/11] ucm: removed unused 'active' member in struct use_case_device Liam Girdwood
2010-12-21 22:11 ` [PATCH 02/11] ucm: modifiers names must be compound parse Liam Girdwood
2010-12-21 22:11 ` [PATCH 03/11] ucm: remove parse_device() and call parse_compound() directly Liam Girdwood
2010-12-21 22:11 ` [PATCH 04/11] ucm: implement basic script exec functionality Liam Girdwood
2010-12-21 22:11 ` [PATCH 05/11] ucm: make sure active modifier and device lists are initialised Liam Girdwood
2010-12-21 22:11 ` [PATCH 06/11] ucm: remove unused code Liam Girdwood
2010-12-21 22:11 ` [PATCH 07/11] ucm: check for valid value list before dereference Liam Girdwood
2010-12-21 22:11 ` [PATCH 08/11] ucm: check the correct return value for modifier Liam Girdwood
2010-12-21 22:11 ` [PATCH 09/11] ucm: only select modifier when supported device is enabled Liam Girdwood
2010-12-21 22:11 ` [PATCH 10/11] ucm: fix handling of cset with spaces in the control name Liam Girdwood
2010-12-21 22:12 ` [PATCH 11/11] ucm: ctlparse - always terminate cset buffer Liam Girdwood
2010-12-22 0:03 ` Mark Brown [this message]
2011-01-11 16:43 ` UCM updates and fixes Liam Girdwood
2011-01-11 16:46 ` Jaroslav Kysela
2011-01-11 17:08 ` Liam Girdwood
2011-01-11 17:12 ` Jaroslav Kysela
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=20101222000339.GD10081@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=lrg@slimlogic.co.uk \
/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