From: Liam Girdwood <lrg@slimlogic.co.uk>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, patches@opensource.wolfsonmicro.com,
Timur Tabi <timur@freescale.com>
Subject: Re: [PATCH] ASoC: Remove module probe announcements from CODEC drivers
Date: Tue, 01 Mar 2011 20:57:52 +0000 [thread overview]
Message-ID: <1299013072.3345.83.camel@odin> (raw)
In-Reply-To: <1299010455-31934-1-git-send-email-broonie@opensource.wolfsonmicro.com>
On Tue, 2011-03-01 at 20:14 +0000, Mark Brown wrote:
> Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
> ---
> sound/soc/codecs/ak4104.c | 1 -
> sound/soc/codecs/cs4270.c | 2 --
> 2 files changed, 0 insertions(+), 3 deletions(-)
>
Acked-by: Liam Girdwood <lrg@slimlogic.co.uk>
prev parent reply other threads:[~2011-03-01 20:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-01 20:14 [PATCH] ASoC: Remove module probe announcements from CODEC drivers Mark Brown
2011-03-01 20:17 ` Timur Tabi
2011-03-01 20:21 ` Mark Brown
2011-03-01 20:57 ` 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=1299013072.3345.83.camel@odin \
--to=lrg@slimlogic.co.uk \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=patches@opensource.wolfsonmicro.com \
--cc=timur@freescale.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).