From: peter.ujfalusi@ti.com (Peter Ujfalusi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/2] dmaengine: omap-dma: Fix polled completion
Date: Tue, 5 Apr 2016 17:50:48 +0300 [thread overview]
Message-ID: <5703D0C8.80509@ti.com> (raw)
In-Reply-To: <20160404131822.GA19738@vkoul-mobl.iind.intel.com>
Hi Vinod,
On 04/04/16 16:18, Vinod Koul wrote:
> On Thu, Mar 10, 2016 at 03:28:45PM +0200, Peter Ujfalusi wrote:
>> Hi,
>>
>> Based on the discussion on the first version:
>> https://lkml.org/lkml/2016/2/25/167
>>
>> I have fixed the omap_dma_tx_status() - first patch and added the second patch
>> to not disable the interrupts for memcpy so multiple transfers can be queued.
>
> Hi Peter,
>
> These do not apply for me. Can you please check.
I have resent as v3.
> FWIW my fixes is on -rc1
tested with -rc1
--
P?ter
prev parent reply other threads:[~2016-04-05 14:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 13:28 [PATCH v2 0/2] dmaengine: omap-dma: Fix polled completion Peter Ujfalusi
2016-03-10 13:28 ` [PATCH v2 1/2] dmaengine: omap-dma: Fix polled channel completion detection and handling Peter Ujfalusi
2016-03-10 13:28 ` [PATCH v2 2/2] dmaengine: omap-dma: Do not suppress interrupts for memcpy Peter Ujfalusi
2016-04-04 13:18 ` [PATCH v2 0/2] dmaengine: omap-dma: Fix polled completion Vinod Koul
2016-04-05 14:50 ` Peter Ujfalusi [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=5703D0C8.80509@ti.com \
--to=peter.ujfalusi@ti.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).