From: vinod.koul@intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RESEND 2/5] dmaengine: Provide a wrapper for memcpy operations
Date: Tue, 31 Jan 2017 09:04:14 +0530 [thread overview]
Message-ID: <20170131033414.GI19244@localhost> (raw)
In-Reply-To: <20170130184721.072c0de1@bbrezillon>
On Mon, Jan 30, 2017 at 06:47:21PM +0100, Boris Brezillon wrote:
> Hi Vinod,
>
> On Mon, 30 Jan 2017 22:24:17 +0530
> Vinod Koul <vinod.koul@intel.com> wrote:
>
> > On Fri, Jan 27, 2017 at 05:42:01PM +0100, Boris Brezillon wrote:
> > > Almost all ->device_prep_dma_xx() methods have a wrapper defined in
> > > dmaengine.h. Add one for ->device_prep_dma_memcpy().
> >
> > Looks good to me.
> >
> > Acked-by: Vinod Koul <vinod.koul@intel.com>
> >
> >
>
> Maybe you can take this patch directly (the NAND related bits are for
> 4.12).
Good idea, applied now..
--
~Vinod
next prev parent reply other threads:[~2017-01-31 3:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-27 16:41 [PATCH RESEND 0/5] mtd: nand: Rework/cleanup the Atmel NAND driver Boris Brezillon
2017-01-27 16:42 ` [PATCH RESEND 1/5] gpio: Add the devm_get_index_gpiod_from_child() helper Boris Brezillon
2017-01-27 16:42 ` [PATCH RESEND 2/5] dmaengine: Provide a wrapper for memcpy operations Boris Brezillon
2017-01-30 16:54 ` Vinod Koul
2017-01-30 17:47 ` Boris Brezillon
2017-01-31 3:34 ` Vinod Koul [this message]
2017-01-27 16:42 ` [PATCH RESEND 4/5] mtd: nand: atmel: Document the new DT bindings Boris Brezillon
2017-02-01 15:39 ` Rob Herring
2017-02-01 15:47 ` Boris Brezillon
2017-02-10 12:55 ` Boris Brezillon
2017-02-10 13:58 ` Rob Herring
2017-02-10 14:00 ` Boris Brezillon
2017-02-13 17:31 ` Nicolas Ferre
2017-01-27 16:42 ` [PATCH RESEND 5/5] mtd: nand: Remove unused chip->write_page() hook Boris Brezillon
[not found] ` <1485535324-28393-4-git-send-email-boris.brezillon@free-electrons.com>
2017-02-14 12:58 ` [PATCH RESEND 3/5] mtd: nand: Cleanup/rework the atmel_nand driver Nicolas Ferre
2017-02-14 13:27 ` Boris Brezillon
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=20170131033414.GI19244@localhost \
--to=vinod.koul@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).