From: Liam Girdwood <lrg@slimlogic.co.uk>
To: Margarita Olaya <magi@slimlogic.co.uk>
Cc: alsa-devel@alsa-project.org,
Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: [PATCH] alsa-lib: ucm: allow values to be read from devices
Date: Wed, 16 Mar 2011 22:27:06 +0000 [thread overview]
Message-ID: <1300314426.8334.0.camel@odin> (raw)
In-Reply-To: <AANLkTikd29BONAW9Zqwrb=tKN1iSVcsig+6Egi1001WD@mail.gmail.com>
On Tue, 2011-03-15 at 10:45 -0600, Margarita Olaya wrote:
> This allows devices value to be read using the get_value().
> Also fix a little formatting.
>
> Signed-off-by: Margarita Olaya Cabrera <magi@slimlogic.co.uk>
Acked-by: Liam Girdwood <lrg@ti.com>
next prev parent reply other threads:[~2011-03-16 22:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-15 16:45 [PATCH] alsa-lib: ucm: allow values to be read from devices Margarita Olaya
2011-03-16 22:27 ` Liam Girdwood [this message]
2011-03-18 15:36 ` Margarita Olaya
2011-03-18 15:44 ` Takashi Iwai
2011-03-18 16:19 ` Margarita Olaya
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=1300314426.8334.0.camel@odin \
--to=lrg@slimlogic.co.uk \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=magi@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;
as well as URLs for NNTP newsgroup(s).