From: Niklas Cassel <cassel@kernel.org>
To: Frank Li <Frank.Li@nxp.com>
Cc: "Vinod Koul" <vkoul@kernel.org>,
"Manivannan Sadhasivam" <mani@kernel.org>,
"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
"Kishon Vijay Abraham I" <kishon@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Christoph Hellwig" <hch@lst.de>,
"Sagi Grimberg" <sagi@grimberg.me>,
"Chaitanya Kulkarni" <kch@nvidia.com>,
"Herbert Xu" <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
"Nicolas Ferre" <nicolas.ferre@microchip.com>,
"Alexandre Belloni" <alexandre.belloni@bootlin.com>,
"Claudiu Beznea" <claudiu.beznea@tuxon.dev>,
"Koichiro Den" <den@valinux.co.jp>,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org, linux-nvme@lists.infradead.org,
mhi@lists.linux.dev, linux-arm-msm@vger.kernel.org,
linux-crypto@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, imx@lists.linux.dev,
"Damien Le Moal" <dlemoal@kernel.org>
Subject: Re: [PATCH v3 0/9] dmaengine: Add new API to combine configuration and descriptor preparation
Date: Mon, 12 Jan 2026 14:01:32 +0100 [thread overview]
Message-ID: <aWTwrOOXX3AR8Ght@ryzen> (raw)
In-Reply-To: <20260105-dma_prep_config-v3-0-a8480362fd42@nxp.com>
Frank,
Thanks a lot for your work on this series!
On Mon, Jan 05, 2026 at 05:46:50PM -0500, Frank Li wrote:
> Documentation/driver-api/dmaengine/client.rst | 9 ++
> drivers/crypto/atmel-aes.c | 10 +--
> drivers/dma/dmaengine.c | 3 +
> drivers/dma/dw-edma/dw-edma-core.c | 41 ++++++---
> drivers/nvme/target/pci-epf.c | 21 ++---
> drivers/pci/endpoint/functions/pci-epf-mhi.c | 52 ++++--------
> drivers/pci/endpoint/functions/pci-epf-test.c | 8 +-
> include/linux/dmaengine.h | 117 ++++++++++++++++++++++++--
> 8 files changed, 177 insertions(+), 84 deletions(-)
Is the plan to merge this series via the dmaengine tree?
If so, we might need an Ack from Mani on the pci-epf-mhi.c and
pci-epf-test.c patch.
Likewise we might need an Ack from Keith/Christoph on the
drivers/nvme/target/pci-epf.c patches.
Kind regards,
Niklas
next prev parent reply other threads:[~2026-01-12 13:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-05 22:46 [PATCH v3 0/9] dmaengine: Add new API to combine configuration and descriptor preparation Frank Li
2026-01-05 22:46 ` [PATCH v3 1/9] dmaengine: Add API to combine configuration and preparation (sg and single) Frank Li
2026-01-05 22:46 ` [PATCH v3 2/9] dmaengine: Add safe API to combine configuration and preparation Frank Li
2026-01-05 22:46 ` [PATCH v3 3/9] PCI: endpoint: pci-epf-test: Use dmaenigne_prep_config_single() to simplify code Frank Li
2026-01-17 10:57 ` Manivannan Sadhasivam
2026-01-05 22:46 ` [PATCH v3 4/9] dmaengine: dw-edma: Use new .device_prep_config_sg() callback Frank Li
2026-01-05 22:46 ` [PATCH v3 5/9] dmaengine: dw-edma: Pass dma_slave_config to dw_edma_device_transfer() Frank Li
2026-01-05 22:46 ` [PATCH v3 6/9] nvmet: pci-epf: Remove unnecessary dmaengine_terminate_sync() on each DMA transfer Frank Li
2026-01-05 22:46 ` [PATCH v3 7/9] nvmet: pci-epf: Use dmaengine_prep_config_single_safe() API Frank Li
2026-01-05 22:46 ` [PATCH v3 8/9] PCI: epf-mhi: Use dmaengine_prep_config_single() to simplify code Frank Li
2026-01-17 11:03 ` Manivannan Sadhasivam
2026-01-05 22:46 ` [PATCH v3 9/9] crypto: atmel: Use dmaengine_prep_config_single() API Frank Li
2026-01-19 9:26 ` Nicolas Ferre
2026-01-12 13:01 ` Niklas Cassel [this message]
2026-01-17 11:05 ` [PATCH v3 0/9] dmaengine: Add new API to combine configuration and descriptor preparation Manivannan Sadhasivam
2026-01-21 16:30 ` Frank Li
2026-01-30 19:19 ` Frank Li
2026-02-25 22:49 ` Niklas Cassel
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=aWTwrOOXX3AR8Ght@ryzen \
--to=cassel@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=alexandre.belloni@bootlin.com \
--cc=bhelgaas@google.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=davem@davemloft.net \
--cc=den@valinux.co.jp \
--cc=dlemoal@kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=hch@lst.de \
--cc=herbert@gondor.apana.org.au \
--cc=imx@lists.linux.dev \
--cc=kch@nvidia.com \
--cc=kishon@kernel.org \
--cc=kwilczynski@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=mani@kernel.org \
--cc=mhi@lists.linux.dev \
--cc=nicolas.ferre@microchip.com \
--cc=sagi@grimberg.me \
--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