linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: dan.j.williams@intel.com (Dan Williams)
To: linux-arm-kernel@lists.infradead.org
Subject: [00/12] DMAENGINE: PL08X driver updates
Date: Sat, 18 Sep 2010 11:52:12 -0700	[thread overview]
Message-ID: <AANLkTi=XH4_0UH8cN_uNzrTmf9GuASe32977gtgUVigU@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi==kKBdOaim+fx5yhpKOo27HWhB7kQiDqv0+BPS@mail.gmail.com>

On Wed, Sep 8, 2010 at 7:26 AM, Linus Walleij
<linus.ml.walleij@gmail.com> wrote:
> 2010/8/31 Linus Walleij <linus.walleij@stericsson.com>:
>
>> This updates the PL08X driver in the async_tx next branch with
>> a number of fixes and features, each one pretty self-describing.
>> This has been tested with the PrimeCell DMA series on the
>> RealView PB11MPCore and works flawlessly, multiplexing
>> several virtual clients, both devices (slaves) and memcpy
>> channels, across only two (!) available physical channels.
>
> Dan can you ACK and queue this for next?
>
> I know you're busy, just a reminder...
>

I'm back at work this coming week and will get all this queued up.

--
Dan

      reply	other threads:[~2010-09-18 18:52 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-31 12:12 [00/12] DMAENGINE: PL08X driver updates Linus Walleij
2010-08-31 12:12 ` [PATCH 01/12] DMAENGINE: remove clock code from PL08X driver Linus Walleij
2010-08-31 12:12   ` [PATCH 02/12] DMAENGINE: safeguard PL08X from missing platform data Linus Walleij
2010-08-31 12:12     ` [PATCH 03/12] DMAENGINE: fetch tasklet struct for PL08X include file Linus Walleij
2010-08-31 12:12       ` [PATCH 04/12] DMAENGINE: use GFP_NOWAIT for PL08X allocations Linus Walleij
2010-08-31 12:12         ` [PATCH 05/12] DMAENGINE: terminate transfers on PL08X mere throughly Linus Walleij
2010-08-31 12:12           ` [PATCH 06/12] DMAENGINE: free txd list if submission fails on PL08X Linus Walleij
2010-08-31 12:12             ` [PATCH 07/12] DMAENGINE: add debugfs file for PL08X Linus Walleij
2010-08-31 12:12               ` [PATCH 08/12] DMAENGINE: be more explicit when freeing PL08X signals Linus Walleij
2010-08-31 12:12                 ` [PATCH 09/12] DMAENGINE: remove pointless module safeguard on PL08X Linus Walleij
2010-08-31 12:12                   ` [PATCH 10/12] DMAENGINE: move the PL08X to full runtime allocation Linus Walleij
2010-08-31 12:12                     ` [PATCH 11/12] DMAENGINE: let PL08X memcpy TXDs wait Linus Walleij
2010-08-31 12:12                       ` [PATCH 12/12] DMAENGINE: define channel states for the PL08X Linus Walleij
2010-09-23  4:59                       ` [PATCH 11/12] DMAENGINE: let PL08X memcpy TXDs wait Dan Williams
2010-09-23  7:39                         ` Linus Walleij
2010-09-23 15:29                           ` Dan Williams
2010-09-23  7:46                         ` Linus Walleij
2010-09-23 15:35                           ` Dan Williams
2010-09-08 14:26 ` [00/12] DMAENGINE: PL08X driver updates Linus Walleij
2010-09-18 18:52   ` Dan Williams [this message]

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='AANLkTi=XH4_0UH8cN_uNzrTmf9GuASe32977gtgUVigU@mail.gmail.com' \
    --to=dan.j.williams@intel.com \
    --cc=linux-arm-kernel@lists.infradead.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).