public inbox for linux-kernel@vger.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] dmaengine fixes for 4.4
Date: Fri, 8 Jan 2016 18:46:29 +0530	[thread overview]
Message-ID: <20160108131629.GL11778@localhost> (raw)

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

Hi Linus

Please pull to receive late fixes for 4.4

The following changes since commit 168309855a7d1e16db751e9c647119fe2d2dc878:

  Linux 4.4-rc8 (2016-01-03 15:15:37 -0800)

are available in the git repository at:

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

for you to fetch changes up to b0b79024627fcbd4b4531f4e2bc8e133c8fb6a95:

  dmaengine: xgene-dma: Fix double IRQ issue by setting IRQ_DISABLE_UNLAZY flag (2016-01-07 11:09:36 +0530)

----------------------------------------------------------------
dmaengine fixes for 4.4

Late fixes for 4.4 are three fixes for drivers which include a
revert of mic-x100 fix which is causing regression, xgene fix for
double IRQ and async_tx fix to use GFP_NOWAIT

----------------------------------------------------------------
Ashutosh Dixit (1):
      dmaengine: Revert "dmaengine: mic_x100: add missing spin_unlock"

NeilBrown (1):
      async_tx: use GFP_NOWAIT rather than GFP_IO

Rameshwar Prasad Sahu (1):
      dmaengine: xgene-dma: Fix double IRQ issue by setting IRQ_DISABLE_UNLAZY flag

 crypto/async_tx/async_memcpy.c      |  2 +-
 crypto/async_tx/async_pq.c          |  4 ++--
 crypto/async_tx/async_raid6_recov.c |  4 ++--
 crypto/async_tx/async_xor.c         |  4 ++--
 drivers/dma/mic_x100_dma.c          | 15 +++++----------
 drivers/dma/xgene-dma.c             |  4 ++++
 6 files changed, 16 insertions(+), 17 deletions(-)

Thanks
-- 
~Vinod

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

                 reply	other threads:[~2016-01-08 13:12 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20160108131629.GL11778@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox