From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Peter Ujfalusi <peter.ujfalusi@nokia.com>
Cc: ext Jorge Eduardo Candelaria <jorge.candelaria@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
lrg@slimlogic.co.uk, tony@atomide.com
Subject: Re: [PATCH v2 0/0] McBSP changes for OMAP4 platform
Date: Wed, 12 May 2010 09:49:30 +0100 [thread overview]
Message-ID: <20100512084930.GA4330@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <201005121139.26990.peter.ujfalusi@nokia.com>
On Wed, May 12, 2010 at 11:39:26AM +0300, Peter Ujfalusi wrote:
> 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.
We've had to do this a few times in the past due to the way the code is
split between the two areas. If it makes everyone's life easier I've
got no problem with it, though I'll say my standard thing about it being
better to keep them on a branch by themselves which can be pulled into
both trees in case of any merge issues.
next prev parent reply other threads:[~2010-05-12 8:49 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 ` [PATCH v2 0/0] McBSP changes for OMAP4 platform Peter Ujfalusi
2010-05-12 8:49 ` Mark Brown [this message]
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=20100512084930.GA4330@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=jorge.candelaria@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=peter.ujfalusi@nokia.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