public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Williams <dan.j.williams@intel.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Li Yang <leoli@freescale.com>, Ira Snyder <iws@ovro.caltech.edu>,
	Timur Tabi <timur@freescale.com>,
	David Hawkins <dwh@ovro.caltech.edu>,
	Liu Dave-R63238 <DaveLiu@freescale.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH] fsldma: use PCI Read Multiple command
Date: Fri, 12 Jun 2009 10:38:00 -0700	[thread overview]
Message-ID: <4A329278.3010607@intel.com> (raw)
In-Reply-To: <24633D89-D4EC-4C27-8B7F-3992EFE50989@kernel.crashing.org>

Kumar Gala wrote:
> On Jun 12, 2009, at 4:23 AM, Li Yang wrote:
> 
>> On Thu, Jun 11, 2009 at 11:17 PM, Ira Snyder<iws@ovro.caltech.edu>  
>> wrote:
>>> On Wed, Jun 10, 2009 at 09:45:26PM -0500, Kumar Gala wrote:
>>>> On Apr 27, 2009, at 3:49 PM, Dan Williams wrote:
>>>>
>>>>> On Mon, Apr 27, 2009 at 1:47 PM, Timur Tabi <timur@freescale.com>
>>>>> wrote:
>>>>>> Adding Kumar to the CC: list, since he might pick up the patch.
>>>>>>
>>>>> Acked-by: Dan Williams <dan.j.williams@intel.com>
>>>>>
>>>>> I agree with taking this through Kumar's tree.
>>>> I'm going through patches for .31.. Should I still pick this up?   
>>>> Going
>>>> forward should I pick up fsldma patches?
>>>>
>>> I'm fine with that, but you should probably talk to Li Yang (added to
>>> CC). He's gotten in contact with me a few times recently.
>> I am fine with both ways for this patch as it is only related to
>> Freescale register details.  But in general I think patches should go
>> through functional subsystem, as they usually would need insight of
>> the subsystem architecture.  I prefer the way that the patch acked or
>> signed-off by Freescale guys and push upstream through Dan's tree as
>> most other subsystems did.  Unless Dan prefers to ack the subsystem
>> architectural part of each patch and have them pushed other way.
> 
> I agree w/this and just wanting to see what Dan's preference is.

I'll take fsldma patches through the dmaengine tree with Leo's 
ack/sign-off.  That last request was a one-off because I had nothing 
else to push and the discussion was very architecture specific.

Thanks,
Dan

  reply	other threads:[~2009-06-12 17:38 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-24 18:35 [PATCH] fsldma: use PCI Read Multiple command Ira Snyder
2009-04-27  7:48 ` Li Yang
2009-04-27  9:09 ` Liu Dave-R63238
2009-04-27 10:16   ` Li Yang
2009-04-27 14:31   ` Timur Tabi
2009-04-27 19:34     ` David Hawkins
2009-04-27 19:40       ` Timur Tabi
2009-04-27 19:48         ` David Hawkins
2009-04-27 19:54           ` Kumar Gala
2009-04-27 20:00             ` David Hawkins
2009-04-27 20:01               ` David Hawkins
2009-04-28  2:06                 ` Liu Dave-R63238
2009-04-27 20:02               ` Kumar Gala
2009-04-27 20:12                 ` David Hawkins
2009-04-27 20:04           ` Timur Tabi
2009-04-27 20:47             ` Scott Wood
2009-04-27 20:49               ` Timur Tabi
2009-04-27 20:22         ` David Hawkins
2009-04-27 20:26           ` Timur Tabi
2009-04-27 20:41             ` David Hawkins
2009-04-27 20:42               ` Timur Tabi
2009-04-27 20:44                 ` David Hawkins
2009-04-27 20:42             ` Ira Snyder
2009-04-27 20:47               ` Timur Tabi
2009-04-27 20:49                 ` Dan Williams
2009-06-11  2:45                   ` Kumar Gala
2009-06-11 15:17                     ` Ira Snyder
2009-06-12  9:23                       ` Li Yang
2009-06-12 15:03                         ` Kumar Gala
2009-06-12 17:38                           ` Dan Williams [this message]
2009-06-12 18:01                             ` Kumar Gala
2009-04-28  1:48       ` Liu Dave-R63238
2009-04-28  2:08         ` David Hawkins
2009-04-28  1:31     ` Liu Dave-R63238
2009-04-28  1:36       ` David Hawkins
2009-04-28 13:43         ` Timur Tabi

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=4A329278.3010607@intel.com \
    --to=dan.j.williams@intel.com \
    --cc=DaveLiu@freescale.com \
    --cc=dwh@ovro.caltech.edu \
    --cc=galak@kernel.crashing.org \
    --cc=iws@ovro.caltech.edu \
    --cc=leoli@freescale.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=timur@freescale.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