From: Robert Jarzmik <robert.jarzmik@free.fr>
To: Vinod Koul <vinod.koul@intel.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
dmaengine@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND 0/2] dmaengine: make transfers reusable
Date: Sun, 07 Jun 2015 21:43:44 +0200 [thread overview]
Message-ID: <87fv63483z.fsf@belgarion.home> (raw)
In-Reply-To: <1432674394-32007-1-git-send-email-robert.jarzmik@free.fr> (Robert Jarzmik's message of "Tue, 26 May 2015 23:06:32 +0200")
Robert Jarzmik <robert.jarzmik@free.fr> writes:
> Hi Vinod and Maxime,
>
> This very same patch was already submitted in [1]. It enables the reuse of
> transfers through their lifetime. I added to this serie the documentation patch
> Maxime has been commenting, as it is tighly linked.
>
> The "RESEND" is a bit zealous as the documentation patch was fixed according to
> Maxime's first 2 comments.
>
> Cheers.
>
> --
> Robert
>
> [1] https://lkml.org/lkml/2015/3/21/230
>
> Robert Jarzmik (2):
> dmaengine: virt-dma: don't always free descriptor upon completion
> Documentation: dmaengine: document DMA_CTRL_ACK
>
> Documentation/dmaengine/provider.txt | 11 ++++++-----
> drivers/dma/virt-dma.c | 19 +++++++++++++------
> drivers/dma/virt-dma.h | 13 ++++++++++++-
> 3 files changed, 31 insertions(+), 12 deletions(-)
Hi Vinod,
Could I get your impressions on this serie ?
Cheers.
--
Robert
next prev parent reply other threads:[~2015-06-07 19:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-26 21:06 [PATCH RESEND 0/2] dmaengine: make transfers reusable Robert Jarzmik
2015-05-26 21:06 ` [PATCH RESEND 1/2] dmaengine: virt-dma: don't always free descriptor upon completion Robert Jarzmik
2015-05-26 21:06 ` [PATCH RESEND 2/2] Documentation: dmaengine: document DMA_CTRL_ACK Robert Jarzmik
2015-06-08 7:13 ` Maxime Ripard
2015-06-07 19:43 ` Robert Jarzmik [this message]
2015-06-17 16:46 ` [PATCH RESEND 0/2] dmaengine: make transfers reusable Vinod Koul
2015-06-17 21:47 ` 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=87fv63483z.fsf@belgarion.home \
--to=robert.jarzmik@free.fr \
--cc=corbet@lwn.net \
--cc=dmaengine@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vinod.koul@intel.com \
/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