linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/2] dmaengine: Add driver documentation
Date: Tue, 28 Oct 2014 22:20:48 +0100	[thread overview]
Message-ID: <20141028212048.GD9255@lukather> (raw)
In-Reply-To: <1414529750-14431-1-git-send-email-maxime.ripard@free-electrons.com>

On Tue, Oct 28, 2014 at 09:55:48PM +0100, Maxime Ripard wrote:
> Hi,
> 
> This is the third attempt at documenting how to write a dmaengine
> driver.
> 
> Changes from v2:
>   - English corrections from Randy Dunlap
>   - Reworked the burst explanations
>   - Reworked the interleaved transfers explanations

And:
  - Removed the	mention	of chancnt
  - Documented DMA_INTERRUPT
  - Various minor addtions/reworks here	and there

-- 
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20141028/664fa124/attachment.sig>

  parent reply	other threads:[~2014-10-28 21:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-28 20:55 [PATCH v3 0/2] dmaengine: Add driver documentation Maxime Ripard
2014-10-28 20:55 ` [PATCH v3 1/2] Documentation: dmaengine: Move the current doc to a folder of its own Maxime Ripard
2014-10-28 20:55 ` [PATCH v3 2/2] Documentation: dmaengine: Add a documentation for the dma controller API Maxime Ripard
2014-10-28 21:20 ` Maxime Ripard [this message]
2014-11-06  5:57 ` [PATCH v3 0/2] dmaengine: Add driver documentation Vinod Koul
2014-11-06  9:59   ` Maxime Ripard

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=20141028212048.GD9255@lukather \
    --to=maxime.ripard@free-electrons.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).