All of lore.kernel.org
 help / color / mirror / Atom feed
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 v6.10
Date: Fri, 21 Jun 2024 15:22:52 +0530	[thread overview]
Message-ID: <ZnVNdBGN49EjDfM_@matsya> (raw)

[-- Attachment #1: Type: text/plain, Size: 2155 bytes --]

Hello Linus,

Last one for the day, please pull to receiev few driver fixes for
dmaengine subsystem.

The following changes since commit 1613e604df0cd359cf2a7fbd9be7a0bcfacfabd0:

  Linux 6.10-rc1 (2024-05-26 15:20:12 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/vkoul/dmaengine.git tags/dmaengine-fix-6.10

for you to fetch changes up to 5422145d0b749ad554ada772133b9b20f9fb0ec8:

  dmaengine: ioatdma: Fix missing kmem_cache_destroy() (2024-06-11 23:39:26 +0530)

----------------------------------------------------------------
dmaengine fixes for v6.10

Driver fixes for:
 - kmemleak, error path handling and missing kmem_cache_destroy() fixes
   for ioatdma driver
 - after use fix for idxd driver
 - data synchronisation fix for xdma isr handling
 - fsl driver channel constraints and linking two fsl module fixes

----------------------------------------------------------------
Arnd Bergmann (1):
      dmaengine: fsl-edma: avoid linking both modules

Krzysztof Kozlowski (1):
      dt-bindings: dma: fsl-edma: fix dma-channels constraints

Li RongQing (1):
      dmaengine: idxd: Fix possible Use-After-Free in irq_process_work_list

Louis Chauvet (1):
      dmaengine: xilinx: xdma: Fix data synchronisation in xdma_channel_isr()

Nikita Shubin (4):
      dmaengine: ioatdma: Fix leaking on version mismatch
      dmaengine: ioatdma: Fix error path in ioat3_dma_probe()
      dmaengine: ioatdma: Fix kmemleak in ioat_pci_probe()
      dmaengine: ioatdma: Fix missing kmem_cache_destroy()

Siddharth Vadapalli (1):
      dmaengine: ti: k3-udma-glue: Fix of_k3_udma_glue_parse_chn_by_id()

 .../devicetree/bindings/dma/fsl,edma.yaml          |  4 +-
 drivers/dma/Kconfig                                |  2 +-
 drivers/dma/idxd/irq.c                             |  4 +-
 drivers/dma/ioat/init.c                            | 55 ++++++++++++----------
 drivers/dma/ti/k3-udma-glue.c                      |  5 +-
 drivers/dma/xilinx/xdma.c                          |  4 +-
 6 files changed, 39 insertions(+), 35 deletions(-)


-- 
~Vinod

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2024-06-21  9:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-21  9:52 Vinod Koul [this message]
2024-06-21 18:10 ` [GIT PULL]: dmaengine fixes for v6.10 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=ZnVNdBGN49EjDfM_@matsya \
    --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 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.