From: Liam Girdwood <lrg@ti.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"patches@opensource.wolfsonmicro.com"
<patches@opensource.wolfsonmicro.com>
Subject: Re: [PATCH 1/2] ASoC: Trigger wm_hubs series update startup off a separate flag
Date: Thu, 23 Jun 2011 13:17:12 +0100 [thread overview]
Message-ID: <4E032EC8.5070707@ti.com> (raw)
In-Reply-To: <1308745217-21062-1-git-send-email-broonie@opensource.wolfsonmicro.com>
On 22/06/11 13:20, Mark Brown wrote:
> Allowing the two to be used independently.
>
> Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
> ---
> sound/soc/codecs/wm8993.c | 1 +
> sound/soc/codecs/wm8994.c | 1 +
> sound/soc/codecs/wm_hubs.c | 3 +--
> sound/soc/codecs/wm_hubs.h | 1 +
> 4 files changed, 4 insertions(+), 2 deletions(-)
>
Both
Acked-by: Liam Girdwood <lrg@ti.com>
prev parent reply other threads:[~2011-06-23 12:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-22 12:20 [PATCH 1/2] ASoC: Trigger wm_hubs series update startup off a separate flag Mark Brown
2011-06-22 12:20 ` [PATCH 2/2] ASoC: Allow suppression of series updates on wm_hubs devices Mark Brown
2011-06-23 12:17 ` Liam Girdwood [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=4E032EC8.5070707@ti.com \
--to=lrg@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=patches@opensource.wolfsonmicro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.