alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Liam Girdwood <lrg@slimlogic.co.uk>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>,
	alsa-devel@alsa-project.org, stable@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ASoC: correct link specifications for corgi, poodle and spitz
Date: Tue, 25 Jan 2011 15:16:30 +0000	[thread overview]
Message-ID: <1295968590.3322.256.camel@odin> (raw)
In-Reply-To: <20110125150317.GG31453@opensource.wolfsonmicro.com>

On Tue, 2011-01-25 at 15:03 +0000, Mark Brown wrote:
> On Fri, Jan 21, 2011 at 10:14:17PM +0300, Dmitry Eremin-Solenikov wrote:
> > ASoC DAI link descriptions for Corgi, Poodle and Spitz platforms
> > contained incorrect names for cpu_dai and codec, which effectievly disabled sound
> > on theese platforms. Fix that errors.
> 
> Ccing in Liam who you forgot to CC - please make sure you CC all
> maintainers on patches.
> 
> > Cc: stable@vger.kernel.org
> > Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
> > ---
> >  sound/soc/pxa/corgi.c  |    4 ++--
> >  sound/soc/pxa/poodle.c |    2 +-
> >  sound/soc/pxa/spitz.c  |    4 ++--
> >  3 files changed, 5 insertions(+), 5 deletions(-)
> >

Looks fine to me.

Acked-by: Liam Girdwood <lrg@slimlogic.co.uk>

-- 
Freelance Developer, SlimLogic Ltd
ASoC and Voltage Regulator Maintainer.
http://www.slimlogic.co.uk

      reply	other threads:[~2011-01-25 15:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-21 19:14 [PATCH] ASoC: correct link specifications for corgi, poodle and spitz Dmitry Eremin-Solenikov
2011-01-25 15:03 ` Mark Brown
2011-01-25 15:16   ` 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=1295968590.3322.256.camel@odin \
    --to=lrg@slimlogic.co.uk \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=dbaryshkov@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=stable@vger.kernel.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 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).