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: dma <dmaengine@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] late dmaengine fixes for 4.5
Date: Fri, 11 Mar 2016 21:54:17 +0530	[thread overview]
Message-ID: <20160311162417.GB13211@localhost> (raw)

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

Hi Linus

Two fixes showed up in last few days, and they should be included in 4.5. So
please consider PULL to recieve two driver fixes, one marked stable.

The following changes since commit f6cede5b49e822ebc41a099fe41ab4989f64e2cb:

  Linux 4.5-rc7 (2016-03-06 14:48:03 -0800)

are available in the git repository at:

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

for you to fetch changes up to 25c5e9626ca4d40928dc9c44f009ce2ed0a739e7:

  dmaengine: at_xdmac: fix residue computation (2016-03-10 16:32:36 +0530)

----------------------------------------------------------------
dmaengine fixes for 4.5

Few more late fixes on drivers nothing major here.
 - A memory leak fix in fsdma unmap the dma descriptors on
   freeup.
 - A fix in xdmac driver for residue calculation of dma
   descriptor.

----------------------------------------------------------------
Ludovic Desroches (1):
      dmaengine: at_xdmac: fix residue computation

Xuelin Shi (1):
      dmaengine: fsldma: fix memory leak

 drivers/dma/at_xdmac.c | 42 +++++++++++++++++++++++++++++++++++++++---
 drivers/dma/fsldma.c   |  2 ++
 2 files changed, 41 insertions(+), 3 deletions(-)
-- 
~Vinod

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

                 reply	other threads:[~2016-03-11 16:20 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=20160311162417.GB13211@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