From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Liam Girdwood <lrg@ti.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: [PATCH 1/2] ASoC: tlv320aic3x: Don't sync first two registers from register cache
Date: Sun, 22 May 2011 18:21:14 +0800 [thread overview]
Message-ID: <20110522102112.GA21476@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4DD7DAAA.3070504@ti.com>
On Sat, May 21, 2011 at 04:30:50PM +0100, Liam Girdwood wrote:
> Both
> Acked-by: Liam Girdwood <lrg@ti.com>
Acked-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
As they're TI devices I guess you'd want to apply them?
next prev parent reply other threads:[~2011-05-22 10:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-20 13:52 [PATCH 1/2] ASoC: tlv320aic3x: Don't sync first two registers from register cache Jarkko Nikula
2011-05-20 13:52 ` [PATCH 2/2] ASoC: tlv320aic3x: Do soft reset to codec when going to bias off state Jarkko Nikula
2011-05-21 15:30 ` [PATCH 1/2] ASoC: tlv320aic3x: Don't sync first two registers from register cache Liam Girdwood
2011-05-22 10:21 ` Mark Brown [this message]
2011-05-23 9:39 ` Liam Girdwood
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=20110522102112.GA21476@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=lrg@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;
as well as URLs for NNTP newsgroup(s).