mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Dan Williams" <dan.j.williams@intel.com>
To: "Kumar Gala" <galak@kernel.crashing.org>
Cc: "LKML Kernel" <linux-kernel@vger.kernel.org>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"Zhang Wei" <wei.zhang@freescale.com>
Subject: Re: dma engine drivers for 2.6.25?
Date: Thu, 14 Feb 2008 22:29:11 -0700	[thread overview]
Message-ID: <e9c3a7c20802142129m51acf21amc48eaea5db45840b@mail.gmail.com> (raw)
In-Reply-To: <DC488215-D313-41E0-A98A-1C90D02A465D@kernel.crashing.org>

On Thu, Feb 14, 2008 at 8:44 PM, Kumar Gala <galak@kernel.crashing.org> wrote:
>
>  On Feb 14, 2008, at 12:14 PM, Dan Williams wrote:
>
>  > On Wed, Feb 13, 2008 at 8:52 PM, Kumar Gala
>  > <galak@kernel.crashing.org> wrote:
>  >> Dan,
>  >>
>  >> What's going on with the dma engine drivers for 2.6.25?  We had a
>  >> Freescale dma driver from Zhang Wei queued up but seems to have been
>  >> lost.
>  >
>  > I pulled it into my tree and am holding it until Zhang has an
>  > opportunity to address the pending review comments [1].  I also did
>  > not feel comfortable pushing it to Linus without a PPC maintainer's
>  > Acked-by/Reviewed-by.
>  >
>  > I have attached the version I am carrying.
>
>  What issues are still open.  I was under the belief that Zhang had
>  resolved all the issues.
>

The high priority review item is that the driver performs operation
completion callbacks in hardirq context.  Clients of the API assume
that callbacks will happen in softirq context.  Of lesser concern is
the use of GFP_ATOMIC in fsl_dma_alloc_descriptor.  Other drivers
preallocate a small pool of descriptors.

Regards,
Dan

  reply	other threads:[~2008-02-15  5:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-14  3:52 Kumar Gala
2008-02-14 18:14 ` Dan Williams
2008-02-15  3:44   ` Kumar Gala
2008-02-15  5:29     ` Dan Williams [this message]
2008-02-24  2:06       ` Dan Williams
2008-02-25 10:25         ` Zhang Wei

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=e9c3a7c20802142129m51acf21amc48eaea5db45840b@mail.gmail.com \
    --to=dan.j.williams@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=galak@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wei.zhang@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

all inboxes | Powered by JetHome®