linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Williams <dan.j.williams@intel.com>
To: Linus Walleij <linus.walleij@stericsson.com>
Cc: akpm@linux-foundation.org,
	Russell King - ARM Linux <linux@arm.linux.org.uk>,
	Grant Likely <grant.likely@secretlab.ca>,
	linux-arm-kernel@lists.infradead.org, linux-mmc@vger.kernel.org,
	STEricsson_nomadik_linux@list.st.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 00/11] ARM: PrimeCell DMA Interface v5
Date: Wed, 7 Apr 2010 16:45:54 -0700	[thread overview]
Message-ID: <v2se9c3a7c21004071645u8180f4d7p3b4b1f96de11303e@mail.gmail.com> (raw)
In-Reply-To: <1270681920-4461-1-git-send-email-linus.walleij@stericsson.com>

Hi Linus, back online now.

On Wed, Apr 7, 2010 at 4:12 PM, Linus Walleij
<linus.walleij@stericsson.com> wrote:
> This is the fifth iteration of this ever growing patch set
> for PrimeCell DMA support, reposting the entire series.
>
> This now depend on stuff pending in Dan Williams async_tx
> (DMA Devices/Engine) tree and Andrew Mortons tree where
> the new DMA40 driver for U8500 is queued.
>
> I suggest putting these into Andrews tree now, since:
>
> A) 4 of the patches it touches MMCI code which is hanled
>   by Andrew
>

Ok, but it looks like they do not have a build dependency on dma bits
so they could be merged separately i.e. on top of the async_tx branch.

> B) It extends the DMA40 driver which is now pending in
>   his tree as well.
>
> C) Since there doesn't seem to be any consensus of whether
>   this is the right way forward, it needs some wider
>   testing I believe.

No consensus with respect to which pieces, the Primecell driver or
something outside of drivers/dma?  Forgive me for missing recent
conversations if this has been discussed to death already.

> OK?

I can go ahead and queue up the dma bits unless you would prefer, and
Andrew agrees, to take this all through the -mm tree?

--
Dan

  reply	other threads:[~2010-04-07 23:45 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-07 23:12 [PATCH 00/11] ARM: PrimeCell DMA Interface v5 Linus Walleij
2010-04-07 23:45 ` Dan Williams [this message]
2010-04-08  6:35   ` Linus WALLEIJ
2010-04-11 14:13     ` Linus Walleij
2010-04-12 19:23       ` Russell King - ARM Linux
2010-04-15  1:15     ` Dan Williams
2010-04-17  4:58       ` Linus Walleij
2010-04-22 11:00         ` Russell King - ARM Linux
2010-04-30 18:30           ` Linus Walleij
2010-05-01 22:00           ` Dan Williams
2010-05-01 22:27             ` Linus Walleij
2010-05-01 22:44             ` Russell King - ARM Linux
2010-05-01 23:04               ` Linus Walleij
2010-05-01 23:28                 ` Russell King - ARM Linux
2010-05-02  0:21                   ` Linus Walleij
2010-05-02  8:18                     ` Russell King - ARM Linux
2010-05-04 13:05                       ` Linus WALLEIJ
2010-05-01 23:28                 ` Dan Williams
2010-05-01 23:48                   ` Linus Walleij
2010-05-01 23:25               ` Dan Williams

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=v2se9c3a7c21004071645u8180f4d7p3b4b1f96de11303e@mail.gmail.com \
    --to=dan.j.williams@intel.com \
    --cc=STEricsson_nomadik_linux@list.st.com \
    --cc=akpm@linux-foundation.org \
    --cc=grant.likely@secretlab.ca \
    --cc=linus.walleij@stericsson.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux@arm.linux.org.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).