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: Wed, 1 Feb 2017 21:42:54 +0530 [thread overview]
Message-ID: <20170201161254.GO19244@localhost> (raw)
[-- Attachment #1: Type: text/plain, Size: 1358 bytes --]
Hey Linus,
Couple of fixes showed up late in the cycle so sending them up and sending
early in the week and not on Friday :).
They fix a double lock in pl330 driver and runtime pm fixes for cppi driver.
Please pull.
The following changes since commit 49def1853334396f948dcb4cedb9347abb318df5:
Linux 4.10-rc4 (2017-01-15 16:21:59 -0800)
are available in the git repository at:
git://git.infradead.org/users/vkoul/slave-dma.git tags/dmaengine-fix-4.10-rc7
for you to fetch changes up to 91539eb1fda2d530d3b268eef542c5414e54bf1a:
dmaengine: pl330: fix double lock (2017-01-25 15:35:11 +0530)
----------------------------------------------------------------
dmaengine-fix-4.10-rc7
Few late fixes for this cycle
- pl330 double lock fix
- more fixes for runtime pm handling on cppi
----------------------------------------------------------------
Iago Abal (1):
dmaengine: pl330: fix double lock
Tony Lindgren (3):
dmaengine: cppi41: Fix runtime PM timeouts with USB mass storage
dmaengine: cppi41: Fix oops in cppi41_runtime_resume
dmaengine: cppi41: Clean up pointless warnings
drivers/dma/cppi41.c | 69 ++++++++++++++++++++++++++++++++++------------------
drivers/dma/pl330.c | 19 +++++----------
2 files changed, 52 insertions(+), 36 deletions(-)
Thanks
--
~Vinod
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next reply other threads:[~2017-02-01 16:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-01 16:12 Vinod Koul [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-08-18 17:18 [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=20170201161254.GO19244@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.