From: Vinod Koul <vkoul@kernel.org>
To: Dave Jiang <dave.jiang@intel.com>
Cc: Frank.Li@oss.nxp.com, Dan Williams <djbw@kernel.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
Frank Li <Frank.Li@kernel.org>, Jon Mason <jdmason@kudzu.us>,
Allen Hubbe <allenbh@gmail.com>, Ard Biesheuvel <ardb@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Eric Biggers <ebiggers@kernel.org>,
"open list:CRYPTO API" <linux-crypto@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
"open list:DMA GENERIC OFFLOAD ENGINE SUBSYSTEM"
<dmaengine@vger.kernel.org>,
"open list:NTB DRIVER CORE" <ntb@lists.linux.dev>,
imx@lists.linux.dev, Frank Li <Frank.Li@nxp.com>
Subject: Re: [PATCH 1/1] dmaengine: change dmaengine_get_unmap_data() first arg to dma_chan
Date: Fri, 9 Oct 2026 11:43:35 +0200 [thread overview]
Message-ID: <asi3R24SY-Y2wJQx@parshuram> (raw)
In-Reply-To: <b40fa0d7-fbd0-4ee8-b99c-781d08c18838@intel.com>
On 22-09-26, 16:09, Dave Jiang wrote:
>
>
> On 9/22/26 11:45 AM, Frank.Li@oss.nxp.com wrote:
> > From: Frank Li <Frank.Li@nxp.com>
> >
> > Replace the struct device *dev argument with struct dma_chan *chan so
> > callers do not need to reach into the dma_device internals to obtain
> > the device pointer. The implementation now derives the device via
> > dmaengine_get_dma_device(chan), which correctly handles the per-channel
> > IOMMU mapping case.
> >
> > Prepare to make dma_device private and make dmaengine API consistent.
> >
> > Signed-off-by: Frank Li <Frank.Li@nxp.com>
>
> For the NTB bits:
> Acked-by: Dave Jiang <dave.jiang@intel.com>
>
>
> > ---
> > crypto/async_tx/async_memcpy.c | 4 ++--
> > crypto/async_tx/async_pq.c | 4 ++--
> > crypto/async_tx/async_raid6_recov.c | 4 ++--
> > crypto/async_tx/async_xor.c | 8 ++++----
>
> Maybe one day Dan's wishes will become true and someone will finally deprecate async_tx....
Does Intel still have use it. I am looking at fixing the names and we
can drop async_tx completely...?
--
~Vinod
prev parent reply other threads:[~2026-10-09 9:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 18:45 [PATCH 1/1] dmaengine: change dmaengine_get_unmap_data() first arg to dma_chan Frank.Li
2026-09-22 23:09 ` Dave Jiang
2026-10-09 9:43 ` Vinod Koul [this message]
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=asi3R24SY-Y2wJQx@parshuram \
--to=vkoul@kernel.org \
--cc=Frank.Li@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=Frank.Li@oss.nxp.com \
--cc=akpm@linux-foundation.org \
--cc=allenbh@gmail.com \
--cc=ardb@kernel.org \
--cc=dave.jiang@intel.com \
--cc=davem@davemloft.net \
--cc=djbw@kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=ebiggers@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=imx@lists.linux.dev \
--cc=jdmason@kudzu.us \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ntb@lists.linux.dev \
/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