From: Takashi Iwai <tiwai@suse.de>
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: Fri, 18 Mar 2011 16:44:59 +0100 [thread overview]
Message-ID: <s5h1v24touc.wl%tiwai@suse.de> (raw)
In-Reply-To: <AANLkTikd29BONAW9Zqwrb=tKN1iSVcsig+6Egi1001WD@mail.gmail.com>
At Tue, 15 Mar 2011 10:45:19 -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>
> ---
> src/ucm/main.c | 19 +++++++++++++------
> 1 files changed, 13 insertions(+), 6 deletions(-)
>
> diff --git a/src/ucm/main.c b/src/ucm/main.c
> index 42fd373..fb11e61 100644
> --- a/src/ucm/main.c
> +++ b/src/ucm/main.c
> @@ -1063,20 +1063,27 @@ static int get_value3(const char **value,
> * \return Zero on success (value is filled), otherwise a negative error code
> */
> static int get_value(snd_use_case_mgr_t *uc_mgr,
> - const char *identifier,
> - const char **value,
> - const char *modifier)
> + const char *identifier,
> + const char **value,
> + const char *item)
Please fix also the corresponding DocBook comment when you change the
parameter (and semantics).
> + dev = find_device(uc_mgr->active_verb, item);
> + if (dev != NULL) {
> + err = get_value1(value, &dev->value_list, identifier);
> + if (err >=0 || err != -ENOENT)
Put a space after '>='.
Could you resubmit with these fixes?
thanks,
Takashi
next prev parent reply other threads:[~2011-03-18 15:45 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
2011-03-18 15:36 ` Margarita Olaya
2011-03-18 15:44 ` Takashi Iwai [this message]
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=s5h1v24touc.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--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).