From: Vinod Koul <vkoul@kernel.org>
To: Andrey Smirnov <andrew.smirnov@gmail.com>
Cc: dmaengine@vger.kernel.org, Stefan Agner <stefan@agner.ch>,
Chris Healy <cphealy@gmail.com>,
linux-imx@nxp.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dmaengine: fsl-edma: implement .device_synchronize callback
Date: Thu, 8 Aug 2019 19:02:06 +0530 [thread overview]
Message-ID: <20190808133206.GB12733@vkoul-mobl.Dlink> (raw)
In-Reply-To: <20190731173659.14778-1-andrew.smirnov@gmail.com>
On 31-07-19, 10:36, Andrey Smirnov wrote:
> Implement .device_synchronize callback in order to be able to use
> dmaengine_terminate_sync() and other primitives relying on said
> callback.
Applied, thanks
--
~Vinod
prev parent reply other threads:[~2019-08-08 13:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-31 17:36 [PATCH] dmaengine: fsl-edma: implement .device_synchronize callback Andrey Smirnov
2019-08-08 13:32 ` Vinod Koul [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=20190808133206.GB12733@vkoul-mobl.Dlink \
--to=vkoul@kernel.org \
--cc=andrew.smirnov@gmail.com \
--cc=cphealy@gmail.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stefan@agner.ch \
/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).