All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul@intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>, dma <dmaengine@vger.kernel.org>
Subject: [GIT PULL] late dmaengine fixes
Date: Tue, 18 Aug 2015 22:48:00 +0530	[thread overview]
Message-ID: <20150818171800.GZ13546@localhost> (raw)

[-- Attachment #1: Type: text/plain, Size: 1088 bytes --]

Hi Linus,

We have a small fix for dmaengine privatecnt disbalance in
dma_request_slave_channel() API. Please consider pulling to fix this issue
reported on few devices from users

The following changes since commit 2c6625cd545bdd66acff14f3394865d43920a5c7:

  Linux 4.2-rc7 (2015-08-16 16:34:13 -0700)

are available in the git repository at:

  git://git.infradead.org/users/vkoul/slave-dma.git tags/dmaengine-fix-4.2-rc8

for you to fetch changes up to 05aa1a77dcf1b9f9c4fedf09a0a53e15d6b21738:

  dmaengine: fix balance of privatecnt inc/dec operations (2015-08-17 22:47:43 +0530)

----------------------------------------------------------------
dmaengine fixes for 4.2-rc7

We recently found issue with dma_request_slave_channel() API causing
privatecnt value to go bad. This is fixed by balancing the privatecnt

----------------------------------------------------------------
Robert Baldyga (1):
      dmaengine: fix balance of privatecnt inc/dec operations

 drivers/dma/dmaengine.c | 4 ++++
 1 file changed, 4 insertions(+)

Thanks
-- 
~Vinod

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

             reply	other threads:[~2015-08-18 17:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-18 17:18 Vinod Koul [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-02-01 16:12 [GIT PULL] late dmaengine fixes 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=20150818171800.GZ13546@localhost \
    --to=vinod.koul@intel.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 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.