From: Vinod Koul <vkoul@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: dma <dmaengine@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] dmaengine late fixes for 5.3
Date: Sat, 7 Sep 2019 13:42:34 +0530 [thread overview]
Message-ID: <20190907081234.GJ2672@vkoul-mobl> (raw)
Heya Linus,
I would like you to pull for couple of simple dmaengine driver fixes we
got in last few days.
The following changes since commit d1abaeb3be7b5fa6d7a1fbbd2e14e3310005c4c1:
Linux 5.3-rc5 (2019-08-18 14:31:08 -0700)
are available in the Git repository at:
git://git.infradead.org/users/vkoul/slave-dma.git tags/dmaengine-fix-5.3
for you to fetch changes up to cf24aac38698bfa1d021afd3883df3c4c65143a4:
dmaengine: rcar-dmac: Fix DMACHCLR handling if iommu is mapped (2019-09-04 11:35:58 +0530)
----------------------------------------------------------------
dmaengine late fixes for 5.3
Some late fixes for drivers:
- memory leak in ti crossbar dma driver
- cleanup of omap dma probe
- Fix for link list configuration in sprd dma driver
- Handling fixed for DMACHCLR if iommu is mapped in rcar dma
----------------------------------------------------------------
Baolin Wang (1):
dmaengine: sprd: Fix the DMA link-list configuration
Wenwen Wang (2):
dmaengine: ti: dma-crossbar: Fix a memory leak bug
dmaengine: ti: omap-dma: Add cleanup in omap_dma_probe()
Yoshihiro Shimoda (1):
dmaengine: rcar-dmac: Fix DMACHCLR handling if iommu is mapped
drivers/dma/sh/rcar-dmac.c | 28 +++++++++++++++++++---------
drivers/dma/sprd-dma.c | 10 ++++++++--
drivers/dma/ti/dma-crossbar.c | 4 +++-
drivers/dma/ti/omap-dma.c | 4 +++-
4 files changed, 33 insertions(+), 13 deletions(-)
Thanks
--
~Vinod
next reply other threads:[~2019-09-07 8:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-07 8:12 Vinod Koul [this message]
2019-09-07 17:10 ` [GIT PULL] dmaengine late fixes for 5.3 pr-tracker-bot
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=20190907081234.GJ2672@vkoul-mobl \
--to=vkoul@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).