From: Peter Ujfalusi <peter.ujfalusi@nokia.com>
To: ext Jorge Eduardo Candelaria <jorge.candelaria@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
lrg@slimlogic.co.uk, tony@atomide.com,
broonie@opensource.wolfsonmicro.com
Subject: Re: [PATCH v2 0/0] McBSP changes for OMAP4 platform
Date: Wed, 12 May 2010 11:39:26 +0300 [thread overview]
Message-ID: <201005121139.26990.peter.ujfalusi@nokia.com> (raw)
In-Reply-To: <1273108546-2507-1-git-send-email-jorge.candelaria@ti.com>
Hi,
On Thursday 06 May 2010 04:15:44 ext Jorge Eduardo Candelaria wrote:
> The following patches enable McBSP driver to be used along with the
> audio driver in SDP4430 and other OMAP4 based boards.
>
> Changes from v1:
> - Changed to correct IRQ lines.
> - Check if rx_irq is defined, instead of checking if cpu is omap4
>
> Jorge Eduardo Candelaria (2):
> ARM: McBSP: Fix request for irq in OMAP4
> ARM: OMAP4: Add support for omap4 in McBSP driver
>
> arch/arm/mach-omap2/mcbsp.c | 12 ++++--------
> arch/arm/plat-omap/mcbsp.c | 34 +++++++++++++++++++---------------
> 2 files changed, 23 insertions(+), 23 deletions(-)
Looks good with Jarkko's comment.
However, I'd like to ask Tony, Liam, Jarkko, and Mark the following:
Would it make sense to use the alsa tree for OMAP McBSP related patches, while
keeping l-o in CC off course.
If we have patches for mcbsp pending in l-o and in alsa tree, than we are going
to have hard times to sort things out when they need to be merged.
I'm asking this, because I will also have some patches for mcbsp, which will
need change in arch/ and in sound/ as well.
I know that taking patches to alsa tree for the arch/ is unorthodox, but it will
ease up our life in a long run...
What do you think?
--
Péter
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-05-12 8:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-06 1:15 [PATCH v2 0/0] McBSP changes for OMAP4 platform Jorge Eduardo Candelaria
2010-05-06 1:15 ` [PATCH v2 1/2] ARM: McBSP: Fix request for irq in OMAP4 Jorge Eduardo Candelaria
2010-05-06 1:15 ` [PATCH v2 2/2] ARM: McBSP: Add support for omap4 in McBSP driver Jorge Eduardo Candelaria
2010-05-12 8:15 ` Jarkko Nikula
2010-05-12 8:09 ` [PATCH v2 1/2] ARM: McBSP: Fix request for irq in OMAP4 Jarkko Nikula
2010-05-12 8:39 ` Peter Ujfalusi [this message]
2010-05-12 8:49 ` [PATCH v2 0/0] McBSP changes for OMAP4 platform Mark Brown
2010-05-12 9:07 ` Liam Girdwood
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=201005121139.26990.peter.ujfalusi@nokia.com \
--to=peter.ujfalusi@nokia.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=jorge.candelaria@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--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