From: Vinod Koul <vkoul@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: [GIT PULL]: dmaengine fixes for v5.11
Date: Sat, 9 Jan 2021 14:31:24 +0530 [thread overview]
Message-ID: <20210109090124.GY2771@vkoul-mobl> (raw)
[-- Attachment #1: Type: text/plain, Size: 3114 bytes --]
Hello Linus,
Please pull to receive fixes for dmaengine drivers. Odd fixes for few
drivers.
The following changes since commit 5c8fe583cce542aa0b84adc939ce85293de36e5e:
Linux 5.11-rc1 (2020-12-27 15:30:22 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/vkoul/dmaengine.git tags/dmaengine-fix-5.11
for you to fetch changes up to e1263f9277bad198c2acc8092a41aea1edbea0e4:
dmaengine: stm32-mdma: fix STM32_MDMA_VERY_HIGH_PRIORITY value (2021-01-04 21:27:45 +0530)
----------------------------------------------------------------
dmaengine fixes for v5.11
Bunch of dmaengine driver fixes for:
- coverity discovered issues for xilinx driver
- qcom, gpi driver fix for undefined bhaviour and one off cleanup
- Update Peter's email for TI DMA drivers
- one off for idxd driver
- resource leak fix for mediatek and milbeaut drivers
----------------------------------------------------------------
Amelie Delaunay (1):
dmaengine: stm32-mdma: fix STM32_MDMA_VERY_HIGH_PRIORITY value
Arnd Bergmann (1):
dmaengine: qcom: fix gpi undefined behavior
Christophe JAILLET (2):
dmaengine: mediatek: mtk-hsdma: Fix a resource leak in the error handling path of the probe function
dmaengine: milbeaut-xdmac: Fix a resource leak in the error handling path of the probe function
Dan Carpenter (2):
dmaengine: idxd: off by one in cleanup code
dmaengine: dw-edma: Fix use after free in dw_edma_alloc_chunk()
Peter Ujfalusi (3):
dmaengine: ti: k3-udma: Fix pktdma rchan TPL level setup
MAINTAINERS: Add entry for Texas Instruments DMA drivers
dt-bindings: dma: ti: Update maintainer and author information
Shravya Kumbham (3):
dmaengine: xilinx_dma: check dma_async_device_register return value
dmaengine: xilinx_dma: fix incompatible param warning in _child_probe()
dmaengine: xilinx_dma: fix mixed_enum_type coverity warning
Xiaoming Ni (1):
dmaengine: qcom: gpi: Fixes a format mismatch
Zheng Yongjun (1):
qcom: bam_dma: Delete useless kfree code
Documentation/devicetree/bindings/dma/ti/k3-bcdma.yaml | 4 +++-
Documentation/devicetree/bindings/dma/ti/k3-pktdma.yaml | 4 +++-
Documentation/devicetree/bindings/dma/ti/k3-udma.yaml | 4 +++-
MAINTAINERS | 13 +++++++++++++
drivers/dma/dw-edma/dw-edma-core.c | 4 ++--
drivers/dma/idxd/sysfs.c | 4 ++--
drivers/dma/mediatek/mtk-hsdma.c | 1 +
drivers/dma/milbeaut-xdmac.c | 4 +++-
drivers/dma/qcom/bam_dma.c | 6 +-----
drivers/dma/qcom/gpi.c | 10 +++++-----
drivers/dma/stm32-mdma.c | 2 +-
drivers/dma/ti/k3-udma.c | 6 +++---
drivers/dma/xilinx/xilinx_dma.c | 11 ++++++++---
13 files changed, 48 insertions(+), 25 deletions(-)
--
~Vinod
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2021-01-09 9:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-09 9:01 Vinod Koul [this message]
2021-01-09 19:51 ` pr-tracker-bot
2021-02-10 10:00 [GIT PULL] " Vinod Koul
2021-02-10 20:19 ` 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=20210109090124.GY2771@vkoul-mobl \
--to=vkoul@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
all inboxes | Powered by JetHome®