From: Vinod Koul <vkoul@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: dma <dmaengine@vger.kernel.org>
Subject: [GIT PULL]: Dmaengine subsystem fixes for v6.14
Date: Sun, 2 Mar 2025 23:00:26 +0530 [thread overview]
Message-ID: <Z8SVslyQKIe41xET@vaman> (raw)
[-- Attachment #1: Type: text/plain, Size: 1422 bytes --]
Hello Linus,
Please pull to receive two fixes for tegra adma driver and revert of
one qcom patch causing regressions.
The following changes since commit 2014c95afecee3e76ca4a56956a936e23283f05b:
Linux 6.14-rc1 (2025-02-02 15:39:26 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/vkoul/dmaengine.git tags/dmaengine-fix-6.14
for you to fetch changes up to e521f516716de7895acd1b5b7fac788214a390b9:
dmaengine: Revert "dmaengine: qcom: bam_dma: Avoid writing unavailable register" (2025-02-27 13:29:15 +0530)
----------------------------------------------------------------
dmaengine fixes for v6.14
Driver fixes for:
- tegra210 adma div_u64 divison and max page fixes
- Qualcomm Revert of unavailable register workaround which is causing
regression, fixes have been proposed but still gaps are present so revert
this for now
----------------------------------------------------------------
Caleb Connolly (1):
dmaengine: Revert "dmaengine: qcom: bam_dma: Avoid writing unavailable register"
Mohan Kumar D (2):
dmaengine: tegra210-adma: Use div_u64 for 64 bit division
dmaengine: tegra210-adma: check for adma max page
drivers/dma/qcom/bam_dma.c | 24 ++++++++----------------
drivers/dma/tegra210-adma.c | 20 ++++++++++++++++----
2 files changed, 24 insertions(+), 20 deletions(-)
--
~Vinod
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2025-03-02 17:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-02 17:30 Vinod Koul [this message]
2025-03-02 18:19 ` [GIT PULL]: Dmaengine subsystem fixes for v6.14 pr-tracker-bot
2025-03-14 18:16 ` Jerry Snitselaar
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=Z8SVslyQKIe41xET@vaman \
--to=vkoul@kernel.org \
--cc=dmaengine@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.