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 fixes for v6.2
Date: Fri, 20 Jan 2023 20:35:50 +0530 [thread overview]
Message-ID: <Y8qtzmmIEH+zN7Bm@matsya> (raw)
[-- Attachment #1: Type: text/plain, Size: 3124 bytes --]
Hello Linus,
Here is the dmaengine fixes pull request for v6.2. This brings one core
fix, one email update and bunch of small driver fixes.
The following changes since commit 1b929c02afd37871d5afb9d498426f83432e71c2:
Linux 6.2-rc1 (2022-12-25 13:41:39 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/vkoul/dmaengine.git tags/dmaengine-fix-6.2
for you to fetch changes up to 95e5fda3b5f9ed8239b145da3fa01e641cf5d53c:
ptdma: pt_core_execute_cmd() should use spinlock (2023-01-19 18:59:34 +0530)
----------------------------------------------------------------
dmaengine fixes for v6.2
- Jie Hai's email address Update
- double increment of client_count in dma_chan_get()
- Driver fixes for:
- Bunch of idxd driver fixes use after free, probe error handling and
callback on wq disable
- Go tre fix for qcom gpi driver
- ptdma locking fix
- tegra & imx-sdma mem leak fix
----------------------------------------------------------------
Akhil R (1):
dmaengine: tegra: Fix memory leak in terminate_all()
Eric Pilmore (1):
ptdma: pt_core_execute_cmd() should use spinlock
Hui Wang (1):
dmaengine: imx-sdma: Fix a possible memory leak in sdma_transfer_init
Jayesh Choudhary (1):
dmaengine: ti: k3-udma: Do conditional decrement of UDMA_CHAN_RT_PEER_BCNT_REG
Jie Hai (1):
MAINTAINERS: update Jie Hai's email address
Koba Ko (1):
dmaengine: Fix double increment of client_count in dma_chan_get()
Liu Shixin (1):
dmaengine: xilinx_dma: call of_node_put() when breaking out of for_each_child_of_node()
Mohan Kumar (1):
dmaengine: tegra210-adma: fix global intr clear
Peter Harliman Liem (1):
dmaengine: lgm: Move DT parsing after initialization
Reinette Chatre (3):
dmaengine: idxd: Let probe fail when workqueue cannot be enabled
dmaengine: idxd: Prevent use after free on completion memory
dmaengine: idxd: Do not call DMX TX callbacks during workqueue disable
Shawn.Shao (1):
Add exception protection processing for vd in axi_chan_handle_err function
Vijaya Krishna Nivarthi (1):
dmaengine: qcom: gpi: Set link_rx bit on GO TRE for rx operation
MAINTAINERS | 2 +-
drivers/dma/dmaengine.c | 7 ++++---
drivers/dma/dw-axi-dmac/dw-axi-dmac-platform.c | 6 ++++++
drivers/dma/idxd/device.c | 16 +++++++++++++---
drivers/dma/imx-sdma.c | 4 +++-
drivers/dma/lgm/lgm-dma.c | 10 +++++-----
drivers/dma/ptdma/ptdma-dev.c | 7 ++++---
drivers/dma/ptdma/ptdma.h | 2 +-
drivers/dma/qcom/gpi.c | 1 +
drivers/dma/tegra186-gpc-dma.c | 1 +
drivers/dma/tegra210-adma.c | 2 +-
drivers/dma/ti/k3-udma.c | 5 +++--
drivers/dma/xilinx/xilinx_dma.c | 4 +++-
13 files changed, 46 insertions(+), 21 deletions(-)
--
~Vinod
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2023-01-20 15:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-20 15:05 Vinod Koul [this message]
2023-01-20 18:46 ` [GIT PULL]: dmaengine fixes for v6.2 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=Y8qtzmmIEH+zN7Bm@matsya \
--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