From: Liam Girdwood <lrg@ti.com>
To: "Ujfalusi, Peter" <peter.ujfalusi@ti.com>
Cc: Tony Lindgren <tony@atomide.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"Cousson, Benoit" <b-cousson@ti.com>,
Brown <broonie@opensource.wolfsonmicro.com>,
"Guiriec, Sebastien" <s-guiriec@ti.com>,
"Lopez Cruz, Misael" <misael.lopez@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [alsa-devel] [PATCH 0/4] ASoC: OMAP4: McPDM: Fix legacy support
Date: Mon, 22 Aug 2011 08:38:30 +0100 [thread overview]
Message-ID: <4E520776.6090002@ti.com> (raw)
In-Reply-To: <16027879.L0TXnUXE5z@barack>
On 22/08/11 08:13, Ujfalusi, Peter wrote:
> On Friday 19 August 2011 15:04:20 Tony Lindgren wrote:
>> It seems OK to me.
>
> Thanks!
>
>> But for the -rc cycle it has potential for
>> "fixes for features that never worked" flame bait. If you guys
>> are OK to deal with that then go ahead.
>
> Hrm, I have not thought about this. Not sure, if we want to go there...
>
Yeah, lets take it for 3.2
Liam
prev parent reply other threads:[~2011-08-22 7:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-02 11:34 [PATCH 0/4] ASoC: OMAP4: McPDM: Fix legacy support Peter Ujfalusi
2011-08-02 11:34 ` [PATCH 1/4] OMAP: McPDM: Convert McPDM device to omap_device Peter Ujfalusi
2011-08-19 13:02 ` Tony Lindgren
2011-08-02 11:34 ` [PATCH 2/4] OMAP4: hwmod: enable mcpdm hwmod device Peter Ujfalusi
2011-08-19 13:02 ` Tony Lindgren
2011-08-02 11:34 ` [PATCH 3/4] ASoC: omap-mcpdm: Fix threshold and dma configuration Peter Ujfalusi
2011-08-02 15:50 ` Mark Brown
2011-08-02 11:34 ` [PATCH 4/4] ASoC: OMAP4: McPDM: Convert to hwmod/omap_device Peter Ujfalusi
2011-08-02 16:07 ` Mark Brown
2011-08-03 7:58 ` [alsa-devel] " Péter Ujfalusi
2011-08-09 7:27 ` [alsa-devel] [PATCH 0/4] ASoC: OMAP4: McPDM: Fix legacy support Péter Ujfalusi
2011-08-15 11:28 ` Péter Ujfalusi
2011-08-19 13:04 ` Re: [alsa-devel] " Tony Lindgren
2011-08-22 7:13 ` Péter Ujfalusi
2011-08-22 7:38 ` 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=4E520776.6090002@ti.com \
--to=lrg@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=b-cousson@ti.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-omap@vger.kernel.org \
--cc=misael.lopez@ti.com \
--cc=peter.ujfalusi@ti.com \
--cc=s-guiriec@ti.com \
--cc=tony@atomide.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).