All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul@intel.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: linux-kernel@vger.kernel.org, dmaengine@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, nsekhar@ti.com,
	linux-omap@vger.kernel.org, lars@metafoo.de
Subject: Re: [PATCH] dmaengine: edma: Fetch echan->edesc while holding lock in edma_comletion_handler
Date: Mon, 22 Feb 2016 08:21:37 +0530	[thread overview]
Message-ID: <20160222025136.GS19598@localhost> (raw)
In-Reply-To: <1455196668-9327-1-git-send-email-peter.ujfalusi@ti.com>

On Thu, Feb 11, 2016 at 03:17:48PM +0200, Peter Ujfalusi wrote:
> In order to avoid possible race condition when client drivers are using
> dmaengine_terminate_sync() call to disable the channel.

Applied, thanks

-- 
~Vinod

WARNING: multiple messages have this Message-ID (diff)
From: vinod.koul@intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] dmaengine: edma: Fetch echan->edesc while holding lock in edma_comletion_handler
Date: Mon, 22 Feb 2016 08:21:37 +0530	[thread overview]
Message-ID: <20160222025136.GS19598@localhost> (raw)
In-Reply-To: <1455196668-9327-1-git-send-email-peter.ujfalusi@ti.com>

On Thu, Feb 11, 2016 at 03:17:48PM +0200, Peter Ujfalusi wrote:
> In order to avoid possible race condition when client drivers are using
> dmaengine_terminate_sync() call to disable the channel.

Applied, thanks

-- 
~Vinod

  reply	other threads:[~2016-02-22  2:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-11 13:17 [PATCH] dmaengine: edma: Fetch echan->edesc while holding lock in edma_comletion_handler Peter Ujfalusi
2016-02-11 13:17 ` Peter Ujfalusi
2016-02-11 13:17 ` Peter Ujfalusi
2016-02-22  2:51 ` Vinod Koul [this message]
2016-02-22  2:51   ` Vinod Koul

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=20160222025136.GS19598@localhost \
    --to=vinod.koul@intel.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=nsekhar@ti.com \
    --cc=peter.ujfalusi@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.