All of lore.kernel.org
 help / color / mirror / Atom feed
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 updates for v5.18
Date: Thu, 21 Apr 2022 18:17:11 +0530	[thread overview]
Message-ID: <YmFST5F0AdoaM7om@matsya> (raw)

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

Hello Linus,

Please pull to receive the dmanegine fixes for v5.18. This contains
bunch of driver fixes.

The following changes since commit 3123109284176b1532874591f7c81f3837bbdc17:

  Linux 5.18-rc1 (2022-04-03 14:08:21 -0700)

are available in the Git repository at:

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

for you to fetch changes up to 7495a5bbf89f68c8880757c112fd0994f5dba309:

  dt-bindings: dmaengine: qcom: gpi: Add minItems for interrupts (2022-04-20 18:11:20 +0530)

----------------------------------------------------------------
dmaengine fixes for v5.17

Bunch of driver fixes for:
 - idxd device RO checks and device cleanup
 - dw-edma unaligned access and alignment
 - qcom: missing minItems in binding
 - mediatek pm usage fix
 - imx init script

----------------------------------------------------------------
Dave Jiang (6):
      dmaengine: idxd: fix device cleanup on disable
      dmaengine: idxd: match type for retries var in idxd_enqcmds()
      dmaengine: idxd: fix retry value to be constant for duration of function call
      dmaengine: idxd: add RO check for wq max_batch_size write
      dmaengine: idxd: add RO check for wq max_transfer_size write
      dmaengine: idxd: skip clearing device context when device is read-only

Herve Codina (1):
      dmaengine: dw-edma: Fix unaligned 64bit access

Jiapeng Chong (1):
      dmaengine: dw-edma: Fix inconsistent indenting

Kevin Groeneveld (1):
      dmaengine: imx-sdma: fix init of uart scripts

Miaoqian Lin (1):
      dmaengine: imx-sdma: Fix error checking in sdma_event_remap

Vinod Koul (1):
      dt-bindings: dmaengine: qcom: gpi: Add minItems for interrupts

Xiaomeng Tong (1):
      dma: at_xdmac: fix a missing check on list iterator

zhangqilong (1):
      dmaengine: mediatek:Fix PM usage reference leak of mtk_uart_apdma_alloc_chan_resources

 .../devicetree/bindings/dma/qcom,gpi.yaml          |  1 +
 drivers/dma/at_xdmac.c                             | 12 ++++----
 drivers/dma/dw-edma/dw-edma-v0-core.c              | 16 +++++++----
 drivers/dma/idxd/device.c                          |  6 ++--
 drivers/dma/idxd/submit.c                          |  5 ++--
 drivers/dma/idxd/sysfs.c                           |  6 ++++
 drivers/dma/imx-sdma.c                             | 32 +++++++++++-----------
 drivers/dma/mediatek/mtk-uart-apdma.c              |  9 ++++--
 8 files changed, 53 insertions(+), 34 deletions(-)

-- 
~Vinod

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

             reply	other threads:[~2022-04-21 12:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-21 12:47 Vinod Koul [this message]
2022-04-21 23:28 ` [GIT PULL]: dmaengine updates for v5.18 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=YmFST5F0AdoaM7om@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 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.