From: Liam Girdwood <lrg@slimlogic.co.uk>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: linux-tegra@vger.kernel.org, alsa-devel@alsa-project.org,
Stephen Warren <swarren@nvidia.com>,
Mike Rapoport <mike@compulab.co.il>
Subject: Re: [PATCH v3] ASoC: tegra: TrimSlice machine support
Date: Mon, 02 May 2011 19:33:27 +0100 [thread overview]
Message-ID: <1304361207.3263.17.camel@odin> (raw)
In-Reply-To: <20110502092228.GA2916@sirena.org.uk>
On Mon, 2011-05-02 at 10:22 +0100, Mark Brown wrote:
> On Mon, May 02, 2011 at 08:34:20AM +0300, Mike Rapoport wrote:
> > Mark,
> > Any updates on this?
>
> Since you didn't CC Liam he hasn't revewied the patch yet. I've added
> him now.
>
> >
> > On 04/26/11 11:52, Mike Rapoport wrote:
> > > Signed-off-by: Mike Rapoport <mike@compulab.co.il>
> > > ---
> > > v3 changes:
> > > * s/SND_TEGRA_SOC/SND_SOC_TEGRA
> > > * drop 'default' setting in Kconfig
> > >
> > > v2 changes:
> > > * address Stephen and Mark comments
> > > * rebase against Mark's for-next branch
> > > * switch to data based specification of widgets and routes
> > > * explicitly disable unused codec pins
> > >
> > > sound/soc/tegra/Kconfig | 8 ++
> > > sound/soc/tegra/Makefile | 2 +
> > > sound/soc/tegra/trimslice.c | 228 +++++++++++++++++++++++++++++++++++++++++++
> > > 3 files changed, 238 insertions(+), 0 deletions(-)
> > > create mode 100644 sound/soc/tegra/trimslice.c
Acked-by: Liam Girdwood <lrg@ti.com>
next prev parent reply other threads:[~2011-05-02 18:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-26 8:52 [PATCH v3] ASoC: tegra: TrimSlice machine support Mike Rapoport
2011-05-02 5:34 ` Mike Rapoport
[not found] ` <4DBE425C.2030807-UTxiZqZC01RS1MOuV/RT9w@public.gmane.org>
2011-05-02 9:22 ` [alsa-devel] " Mark Brown
2011-05-02 18:33 ` Liam Girdwood [this message]
[not found] ` <1303807962-14833-1-git-send-email-mike-UTxiZqZC01RS1MOuV/RT9w@public.gmane.org>
2011-04-26 15:18 ` Stephen Warren
2011-05-03 17:44 ` 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=1304361207.3263.17.camel@odin \
--to=lrg@slimlogic.co.uk \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-tegra@vger.kernel.org \
--cc=mike@compulab.co.il \
--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