From: Liam Girdwood <lrg@ti.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
Lars-Peter Clausen <lars@metafoo.de>,
"device-drivers-devel@blackfin.uclinux.org"
<device-drivers-devel@blackfin.uclinux.org>,
Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH 0/5] AD1836 updates part two
Date: Thu, 16 Jun 2011 09:35:59 +0100 [thread overview]
Message-ID: <4DF9C06F.5050600@ti.com> (raw)
In-Reply-To: <1308166163-22355-1-git-send-email-vapier@gentoo.org>
On 15/06/11 20:29, Mike Frysinger wrote:
> This replaces the patchset I sent out yesterday. It mostly syncs the
> missing work we had locally with what Lars-Peter did. I guess we can
> omit the "ad1836" -> "ad183x" rename.
>
> Barry Song (1):
> ASoC: AD1836: rename suspend/resume funcs
>
> Mike Frysinger (4):
> ASoC: AD1836: drop unnecessary spi register check
> ASoC: AD1836: fix intermixed tab/space indentation
> ASoC: AD1836: fix codec name
> ASoC: AD1836: clean up comment headers
>
> sound/soc/codecs/ad1836.c | 78 +++++++++++++++++---------------------------
> sound/soc/codecs/ad1836.h | 21 +++---------
> 2 files changed, 36 insertions(+), 63 deletions(-)
>
All
Acked-by: Liam Girdwood <lrg@ti.com>
next prev parent reply other threads:[~2011-06-16 8:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-15 19:29 [PATCH 0/5] AD1836 updates part two Mike Frysinger
2011-06-15 19:29 ` [PATCH 1/5] ASoC: AD1836: drop unnecessary spi register check Mike Frysinger
2011-06-15 19:29 ` [PATCH 2/5] ASoC: AD1836: fix intermixed tab/space indentation Mike Frysinger
2011-06-15 19:29 ` [PATCH 3/5] ASoC: AD1836: fix codec name Mike Frysinger
2011-06-15 19:29 ` [PATCH 4/5] ASoC: AD1836: rename suspend/resume funcs Mike Frysinger
2011-06-15 19:29 ` [PATCH 5/5] ASoC: AD1836: clean up comment headers Mike Frysinger
2011-06-16 8:35 ` Liam Girdwood [this message]
2011-06-16 10:42 ` [PATCH 0/5] AD1836 updates part two Mark Brown
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=4DF9C06F.5050600@ti.com \
--to=lrg@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=device-drivers-devel@blackfin.uclinux.org \
--cc=lars@metafoo.de \
--cc=lrg@slimlogic.co.uk \
--cc=vapier@gentoo.org \
/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.