From: robert.jarzmik@free.fr (Robert Jarzmik)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 6/6] Documentation: dmaengine: document DMA_CTRL_ACK
Date: Mon, 25 May 2015 22:57:10 +0200 [thread overview]
Message-ID: <87r3q41il5.fsf@belgarion.home> (raw)
In-Reply-To: <20150525165257.GI3140@localhost> (Vinod Koul's message of "Mon, 25 May 2015 22:22:57 +0530")
Vinod Koul <vinod.koul@intel.com> writes:
>> > Also, we should still mention that it's !slave API only.
>> Certainly not, it's fully slave API, that's the purpose of this patch.
> Its is not dependent on slave, it cna be used by slave as well as other
> users
You're right Vinod. I will rephrase that : this applies for both slave and
!slave.
Cheers.
--
Robert
next prev parent reply other threads:[~2015-05-25 20:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-14 17:53 [PATCH v3 1/6] Documentation: dmaengine: pxa-dma design Robert Jarzmik
2015-05-14 17:53 ` [PATCH v3 2/6] MAINTAINERS: add pxa dma driver to pxa architecture Robert Jarzmik
2015-05-14 17:53 ` [PATCH v3 3/6] dmaengine: pxa: add pxa dmaengine driver Robert Jarzmik
2015-05-25 16:50 ` Vinod Koul
2015-05-25 20:55 ` Robert Jarzmik
2015-05-14 17:53 ` [PATCH v3 4/6] dmaengine: pxa_dma: add debug information Robert Jarzmik
2015-05-14 17:53 ` [PATCH v3 5/6] dmaengine: pxa_dma: add support for legacy transition Robert Jarzmik
2015-05-14 17:53 ` [PATCH v3 6/6] Documentation: dmaengine: document DMA_CTRL_ACK Robert Jarzmik
2015-05-14 18:38 ` Maxime Ripard
2015-05-14 20:31 ` Robert Jarzmik
2015-05-25 16:52 ` Vinod Koul
2015-05-25 20:57 ` Robert Jarzmik [this message]
2015-05-15 19:11 ` [PATCH v3 1/6] Documentation: dmaengine: pxa-dma design Robert Jarzmik
2015-05-19 18:51 ` Robert Jarzmik
2015-05-25 11:03 ` Robert Jarzmik
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=87r3q41il5.fsf@belgarion.home \
--to=robert.jarzmik@free.fr \
--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).