From: Viresh Kumar <viresh.kumar@linaro.org>
To: Vinod Koul <vinod.koul@intel.com>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Jose Abreu <Jose.Abreu@synopsys.com>,
"dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
vireshk@kernel.org
Subject: Re: dmaengine: dw-dmac: Custom cyclic API (Why?)
Date: Mon, 2 Jan 2017 16:28:25 +0530 [thread overview]
Message-ID: <20170102105825.GI13679@vireshk-i7> (raw)
In-Reply-To: <20170102101802.GX3573@localhost>
On 02-01-17, 15:48, Vinod Koul wrote:
> not sure about non intel ones, viresh?
Not sure really :(
--
viresh
next prev parent reply other threads:[~2017-01-02 10:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-30 11:32 dmaengine: dw-dmac: Custom cyclic API (Why?) Jose Abreu
2016-12-30 12:05 ` Jose Abreu
2017-01-02 8:38 ` Andy Shevchenko
2017-01-02 10:18 ` Vinod Koul
2017-01-02 10:58 ` Viresh Kumar [this message]
2017-01-02 11:30 ` Andy Shevchenko
2017-01-02 13:56 ` Jose Abreu
2017-04-04 16:23 ` Andy Shevchenko
2017-04-04 16:43 ` Jose Abreu
2017-05-22 18:17 ` Andy Shevchenko
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=20170102105825.GI13679@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=Jose.Abreu@synopsys.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vinod.koul@intel.com \
--cc=vireshk@kernel.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