From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Linus Walleij <linus.ml.walleij@gmail.com>
Cc: Dan Williams <dan.j.williams@intel.com>,
Linus WALLEIJ <linus.walleij@stericsson.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
Grant Likely <grant.likely@secretlab.ca>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
STEricsson_nomadik_linux <STEricsson_nomadik_linux@list.st.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 00/11] ARM: PrimeCell DMA Interface v5
Date: Thu, 22 Apr 2010 12:00:25 +0100 [thread overview]
Message-ID: <20100422110025.GC20008@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <q2o63386a3d1004162158v296379fat2b376d5c4c087378@mail.gmail.com>
On Sat, Apr 17, 2010 at 06:58:49AM +0200, Linus Walleij wrote:
> 2010/4/15 Dan Williams <dan.j.williams@intel.com>:
>
> > Getting closer... I have pushed out the dma40 driver (v3), 4, and 6.
>
> That's great!
>
> > The other patch in -mm I could take as well but that needs an ack from
> > Russell.
>
> Nah, I'll push that in through Russells tree hopefully, it needs rebasing on
> the latest board setup code anyway.
>
> > 5 is pending the review comment and 9 does not apply cleanly (does it
> > depend on something in the spi tree?)
>
> OK I'm sending updated versions soon, along with a DMA40 bug fix
> all on top of async_tx instead.
>
> Number 9 fails since it is based on -next where all the #include <slab.h>
> business has taken place, I don't know how that is resolved in the end
> but it now includes that include and applies cleanly on async_tx.
>
> I'll keep working on getting the PL011 and PL180 DMA tested on the
> RealView somehow so those can also be accepted.
So has this (which has now been applied to Dan's tree) been tested
as I asked on Versatile platforms, or do we have something that could
be incompatible with those platforms?
I'm basically not acking or applying these patches until something
along those lines has happened. (And unfortunately I don't have the
resources to apply to this at present.)
next prev parent reply other threads:[~2010-04-30 19:59 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
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 [this message]
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=20100422110025.GC20008@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=STEricsson_nomadik_linux@list.st.com \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=grant.likely@secretlab.ca \
--cc=linus.ml.walleij@gmail.com \
--cc=linus.walleij@stericsson.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
/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).