From: Rosen Penev <rosenp@gmail.com>
To: dmaengine@vger.kernel.org
Cc: Vinod Koul <vkoul@kernel.org>,
Patrice Chotard <patrice.chotard@foss.st.com>,
linux-kernel@vger.kernel.org (open list),
linux-arm-kernel@lists.infradead.org (moderated list:ARM/STI
ARCHITECTURE)
Subject: [PATCH dmaengine 0/2] dmaengine: st_fdma: support COMPILE_TEST
Date: Wed, 5 Nov 2025 18:20:13 -0800 [thread overview]
Message-ID: <20251106022015.84970-1-rosenp@gmail.com> (raw)
First commit fixes compilation under 64-bit and second actually enables
it.
Rosen Penev (2):
dmaengine: st_fdma: change dreg_line to long
dmaengine: st_fdma: add COMPILE_TEST support
drivers/dma/Kconfig | 2 +-
drivers/dma/st_fdma.c | 2 +-
drivers/dma/st_fdma.h | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
--
2.51.2
next reply other threads:[~2025-11-06 2:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-06 2:20 Rosen Penev [this message]
2025-11-06 2:20 ` [PATCH dmaengine 1/2] dmaengine: st_fdma: change dreg_line to long Rosen Penev
2025-11-06 2:20 ` [PATCH dmaengine 2/2] dmaengine: st_fdma: add COMPILE_TEST support Rosen Penev
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=20251106022015.84970-1-rosenp@gmail.com \
--to=rosenp@gmail.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patrice.chotard@foss.st.com \
--cc=vkoul@kernel.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;
as well as URLs for NNTP newsgroup(s).