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: [PULL REQUEST] slave dmaengine fixes
Date: Thu, 4 Jun 2015 21:26:22 +0530 [thread overview]
Message-ID: <20150604155622.GQ3140@localhost> (raw)
Hey Linus,
We have two small fixes on driver, please consider pulling them to receive
fixes for:
- pl330 termination hang fix by Krzysztof
- hsu memory leak fix by Peter
The following changes since commit 5ebe6afaf0057ac3eaeb98defd5456894b446d22:
Linux 4.1-rc2 (2015-05-03 19:22:23 -0700)
are available in the git repository at:
git://git.infradead.org/users/vkoul/slave-dma.git fixes
for you to fetch changes up to 429770823d961187c39df490d49683c467b10065:
dmaengine: hsu: Fix memory leak when stopping a running transfer (2015-06-02 18:33:08 +0530)
----------------------------------------------------------------
Krzysztof Kozlowski (1):
dmaengine: pl330: Fix hang on dmaengine_terminate_all on certain boards
Peter Ujfalusi (1):
dmaengine: hsu: Fix memory leak when stopping a running transfer
drivers/dma/hsu/hsu.c | 5 ++++-
drivers/dma/pl330.c | 3 +++
2 files changed, 7 insertions(+), 1 deletion(-)
--
~Vinod
reply other threads:[~2015-06-04 15:55 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=20150604155622.GQ3140@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