From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Liam Girdwood <lrg@slimlogic.co.uk>
Cc: linux-tegra@vger.kernel.org, alsa-devel@alsa-project.org,
Stephen Warren <swarren@nvidia.com>
Subject: Re: [PATCH 0/7] Tegra ALSA/ASoC driver
Date: Mon, 10 Jan 2011 22:27:39 +0000 [thread overview]
Message-ID: <20110110222739.GC5886@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1294696050.3416.236.camel@odin>
On Mon, Jan 10, 2011 at 09:47:30PM +0000, Liam Girdwood wrote:
> I've had a quick look and all is fine.
> Acked-by: Liam Girdwood <lrg@slimlogic.co.uk>
Applied, thanks, together with a patch renaming the debugfs export.
I'll hold off on making any of my updates here until the merge window is
over so that the matching clock tree updates get a chance to show up in
-next and give me a stable base to work from.
prev parent reply other threads:[~2011-01-10 22:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1294450353-25076-1-git-send-email-swarren@wwwdotorg.org>
2011-01-08 5:36 ` [PATCH 0/7] Tegra ALSA/ASoC driver Stephen Warren
2011-01-08 5:36 ` [PATCH 1/7] ASoC: Export debugfs root dentry Stephen Warren
2011-01-10 11:57 ` Mark Brown
2011-01-08 5:36 ` [PATCH 2/7] ASoC: tegra: Add tegra-das driver Stephen Warren
2011-01-08 5:36 ` [PATCH 3/7] ASoC: tegra: Add tegra-pcm driver Stephen Warren
2011-01-11 7:59 ` Peter Ujfalusi
2011-01-11 16:34 ` Stephen Warren
2011-01-08 5:36 ` [PATCH 4/7] ASoC: tegra: Add tegra-i2s driver Stephen Warren
2011-01-08 5:36 ` [PATCH 5/7] ASoC: tegra: Machine utility code Stephen Warren
2011-01-08 5:36 ` [PATCH 6/7] ASoC: tegra: Harmony machine support Stephen Warren
2011-01-08 5:36 ` [PATCH 7/7] ASoC: tegra: Kconfig and Makefile Stephen Warren
2011-01-09 13:59 ` [PATCH 0/7] Tegra ALSA/ASoC driver Mark Brown
2011-01-10 18:35 ` Mark Brown
2011-01-10 21:47 ` Liam Girdwood
2011-01-10 22:27 ` Mark Brown [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=20110110222739.GC5886@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=linux-tegra@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=swarren@nvidia.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).