From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Jarkko Nikula <jhnikula@gmail.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Janusz Krzysztofik <jkrzyszt@tis.icnet.pl>,
Peter Ujfalusi <peter.ujfalusi@nokia.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [alsa-devel] [RFC][PATCH 1/3 v2] ARM: OMAP: DMA: Add support for DMA channel self linking on OMAP1510
Date: Mon, 24 Aug 2009 23:06:13 +0100 [thread overview]
Message-ID: <20090824220612.GB4338@sirena.org.uk> (raw)
In-Reply-To: <20090824124902.GH7069@atomide.com>
On Mon, Aug 24, 2009 at 03:49:03PM +0300, Tony Lindgren wrote:
> > We should remember that arch/arm/plat-omap/mcbsp.c changes done via
> > ALSA tree has been an exception and that's only for simpler procedure.
> > McBSP is not so critical if sources goes out-of-sync but DMA is.
> Sorry for the delay in replying. I'm OK for these to go in via the alsa
> tree as there are not currently other patches pending in the mcbsp or
> dma area for omap. So I think it's better merge all the audio related
> patches together in this case.
Applied, thanks.
prev parent reply other threads:[~2009-08-24 22:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-10 8:50 [RFC][PATCH 1/3] " Janusz Krzysztofik
2009-08-17 9:16 ` Jarkko Nikula
2009-08-23 15:56 ` [RFC][PATCH 1/3 v2] " Janusz Krzysztofik
2009-08-23 17:03 ` [alsa-devel] " Mark Brown
2009-08-23 17:45 ` Janusz Krzysztofik
2009-08-23 18:05 ` Mark Brown
2009-08-23 18:38 ` Janusz Krzysztofik
2009-08-23 18:49 ` Mark Brown
2009-08-24 5:49 ` Jarkko Nikula
2009-08-24 12:49 ` Tony Lindgren
2009-08-24 22:06 ` Mark Brown [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=20090824220612.GB4338@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=jhnikula@gmail.com \
--cc=jkrzyszt@tis.icnet.pl \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--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
all inboxes | Powered by JetHome®