alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Liam Girdwood <lrg@slimlogic.co.uk>
To: "Candelaria Villareal, Jorge" <jorge.candelaria@ti.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"broonie@opensource.wolfsonmicro.com"
	<broonie@opensource.wolfsonmicro.com>
Subject: Re: [PATCH v4 2/3] ASoC: OMAP4: Add support for McPDM
Date: Tue, 23 Feb 2010 10:13:39 +0000	[thread overview]
Message-ID: <1266920019.3156.5.camel@odin> (raw)
In-Reply-To: <2256F256009DAA4CBE661E9F41EAC84B8FA52BF5@dlee01.ent.ti.com>

On Mon, 2010-02-22 at 17:17 -0600, Candelaria Villareal, Jorge wrote:
> McPDM is the interface between Phoenix audio codec
> and the OMAP4430 processor. It enables data to be transfered
> to/from Phoenix at sample rates of 88.4 or 96 KHz.
> 
> Signed-off-by: Jorge Eduardo Candelaria <jorge.candelaria@ti.com>
> Signed-off-by: Margarita Olaya <x0080101@ti.com>
> ---
> 
> Resending patch to fix an issue reset_playback function
> 

In the future can you increment the patch version number. This way it
makes it easier to see that its different from the previous version.

Since all the previous V4 patches are acked. Can you send this as a diff
to the V4 version.

Thanks

Liam

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

  reply	other threads:[~2010-02-23 10:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-22 23:17 [PATCH v4 2/3] ASoC: OMAP4: Add support for McPDM Candelaria Villareal, Jorge
2010-02-23 10:13 ` Liam Girdwood [this message]
2010-02-23 22:56   ` Candelaria Villareal, Jorge
2010-02-24  9:38     ` Liam Girdwood
  -- strict thread matches above, loose matches on Subject: below --
2010-02-22 21:09 Candelaria Villareal, Jorge

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=1266920019.3156.5.camel@odin \
    --to=lrg@slimlogic.co.uk \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=jorge.candelaria@ti.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).