From: Liam Girdwood <lrg@slimlogic.co.uk>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH 1/3] ASoC: Treat WM8958 revision A as WM8994 revision D
Date: Fri, 18 Mar 2011 09:36:17 +0000 [thread overview]
Message-ID: <1300440977.3539.8.camel@odin> (raw)
In-Reply-To: <1300290532-30555-1-git-send-email-broonie@opensource.wolfsonmicro.com>
On Wed, 2011-03-16 at 15:48 +0000, Mark Brown wrote:
> The first WM8958 revision requires similar treatment.
>
> Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
All
Acked-by: Liam Girdwood <lrg@ti.com>
prev parent reply other threads:[~2011-03-18 9:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-16 15:48 [PATCH 1/3] ASoC: Treat WM8958 revision A as WM8994 revision D Mark Brown
2011-03-16 15:48 ` [PATCH 2/3] ASoC: Factor WM8958 DSP2 handling into separate file Mark Brown
2011-03-16 15:48 ` [PATCH 3/3] ASoC: Handle startup sequencing of WM8958 DSP2 with deferred clocking Mark Brown
2011-03-18 9:36 ` 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=1300440977.3539.8.camel@odin \
--to=lrg@slimlogic.co.uk \
--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 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).