linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Timur Tabi <timur@freescale.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: linuxppc-dev@ozlabs.org, Kumar Gala <kumar.gala@freescale.com>,
	alsa-devel@alsa-project.org, lrg@slimlogic.co.uk
Subject: Re: [alsa-devel] [PATCH 1/2] powerpc/8610: add probing for individual DMA channels, not just DMA controllers
Date: Wed, 05 May 2010 10:59:44 -0500	[thread overview]
Message-ID: <4BE195F0.9070400@freescale.com> (raw)
In-Reply-To: <20100505123545.GA7139@rakim.wolfsonmicro.main>

Mark Brown wrote:
> On Wed, May 05, 2010 at 06:39:01AM -0500, Timur Tabi wrote:
>> On Wed, May 5, 2010 at 6:22 AM, Mark Brown
> 
>>> Just looking at the scheduling here with regard to the merge window and
>>> the fact that this doesn't seem to hurt the existing drivers perhaps it
>>> makes sense to merge this via the PowerPC tree immediately?
> 
>> Aren't we a little late in the cycle for a patch that doesn't do anything?
> 
> It seems to be safe enough for -next.

Sure, -next is fine.

-- 
Timur Tabi
Linux kernel developer at Freescale

  reply	other threads:[~2010-05-05 15:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-03 21:54 [PATCH 1/2] powerpc/8610: add probing for individual DMA channels, not just DMA controllers Timur Tabi
2010-05-04 14:54 ` Mark Brown
2010-05-04 15:11   ` Timur Tabi
2010-05-04 19:22     ` [alsa-devel] " Mark Brown
2010-05-04 17:20 ` Kumar Gala
2010-05-05 11:22   ` Mark Brown
2010-05-05 11:39     ` [alsa-devel] " Timur Tabi
2010-05-05 12:35       ` Mark Brown
2010-05-05 15:59         ` Timur Tabi [this message]
2010-05-17 15:55 ` Kumar Gala

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=4BE195F0.9070400@freescale.com \
    --to=timur@freescale.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=kumar.gala@freescale.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=lrg@slimlogic.co.uk \
    /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).