From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: Tony Lindgren <tony@atomide.com>, Liam Girdwood <lrg@ti.com>,
Jarkko Nikula <jarkko.nikula@bitmer.com>,
linux-omap@vger.kernel.org, alsa-devel@alsa-project.org,
linux-arm-kernel@lists.infradead.org,
Samuel Ortiz <sameo@linux.intel.com>
Subject: Re: [RFC 00/11]O MAP/ASoC: Move and merge McBSP driver under ASoC
Date: Wed, 15 Feb 2012 08:08:10 -0800 [thread overview]
Message-ID: <20120215160809.GF2996@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1329320280-1621-1-git-send-email-peter.ujfalusi@ti.com>
[-- Attachment #1: Type: text/plain, Size: 290 bytes --]
On Wed, Feb 15, 2012 at 05:37:49PM +0200, Peter Ujfalusi wrote:
> Hello,
>
> The aim of this series is to move the plat-omap/mcbsp.c driver out to
> sound/soc/omap/
> By doing this we can combine the two levels of McBSP driver stack into a single
> one.
This all looks OK to me.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-02-15 16:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-15 15:37 [RFC 00/11]O MAP/ASoC: Move and merge McBSP driver under ASoC Peter Ujfalusi
2012-02-15 15:37 ` [RFC 01/11] ARM: OMAP: mcbsp: Convert core driver to proper platform driver Peter Ujfalusi
2012-02-20 17:20 ` Tony Lindgren
2012-02-15 15:37 ` [RFC 02/11] OMAP: mcbsp: Move core driver under sound/soc/omap Peter Ujfalusi
2012-02-20 17:21 ` Tony Lindgren
2012-02-15 15:37 ` [RFC 03/11] ASoC: OMAP: McBSP: Consolidate plat/mcbsp.h content Peter Ujfalusi
2012-02-15 15:37 ` [RFC 04/11] ASoC: core - Add API call to register dai kcontrols Peter Ujfalusi
2012-02-15 15:46 ` Liam Girdwood
2012-02-15 15:52 ` Ujfalusi, Peter
2012-02-15 15:37 ` [RFC 05/11] ASoC: omap-mcbsp: Create a single driver for McBSP Peter Ujfalusi
2012-02-15 15:37 ` [RFC 06/11] ARM: OMAP: Do not register omap-mcbsp-dai device Peter Ujfalusi
2012-02-15 15:37 ` [RFC 07/11] ASoC: OMAP: mcbsp.h: Clean up bit definitions Peter Ujfalusi
2012-02-15 15:37 ` [RFC 08/11] ASoC: OMAP McBSP: Remove redundant accessors Peter Ujfalusi
2012-02-15 15:37 ` [RFC 09/11] ASoC: omap-mcbsp: Cleanup of module probe/remove code Peter Ujfalusi
2012-02-15 15:37 ` [RFC 10/11] ASoC: omap-mcbsp: Merge the omap_mcbsp_data into omap_mcbsp structure Peter Ujfalusi
2012-02-15 15:38 ` [RFC 11/11] ASoC: omap-mcbsp: Simplify DMA configuration Peter Ujfalusi
2012-02-15 15:56 ` [RFC 00/11]O MAP/ASoC: Move and merge McBSP driver under ASoC Ujfalusi, Peter
2012-02-15 19:06 ` Jarkko Nikula
2012-02-20 10:15 ` Janusz Krzysztofik
2012-02-15 16:08 ` Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-02-15 15:37 Peter Ujfalusi
2012-02-18 21:43 ` Grazvydas Ignotas
2012-02-20 8:04 ` Peter Ujfalusi
2012-02-20 20:35 ` Grazvydas Ignotas
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=20120215160809.GF2996@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=jarkko.nikula@bitmer.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@ti.com \
--cc=peter.ujfalusi@ti.com \
--cc=sameo@linux.intel.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).