All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peng Fan <peng.fan@oss.nxp.com>
To: Frank.Li@oss.nxp.com
Cc: Dan Williams <djbw@kernel.org>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	"David S. Miller" <davem@davemloft.net>,
	Vinod Koul <vkoul@kernel.org>, Frank Li <Frank.Li@kernel.org>,
	Jon Mason <jdmason@kudzu.us>, Dave Jiang <dave.jiang@intel.com>,
	Allen Hubbe <allenbh@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Ard Biesheuvel <ardb@kernel.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 v3 1/2] dmaengine: change dmaengine_get_unmap_data() first arg to dma_chan
Date: Thu, 15 Oct 2026 10:55:24 +0800	[thread overview]
Message-ID: <atBAnIzA3X6PgB+6@shlinux89> (raw)
In-Reply-To: <20261014190337.1718622-1-Frank.Li@oss.nxp.com>

Hi Frank,

Seems Patch 2/2 is not sent out?

On Wed, Oct 14, 2026 at 03:03:24PM -0400, 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.
>
>Acked-by: Dave Jiang <dave.jiang@intel.com>
>Signed-off-by: Frank Li <Frank.Li@nxp.com>
>---
>V3 split from origianl thread
>https://lore.kernel.org/dmaengine/20260923-dmaengine_prep_dma_pq-v2-0-32ed65b8a9b4@nxp.com/
>V2 change collect Dave Jiang ack tags
>v1 version at
>https://lore.kernel.org/imx/b40fa0d7-fbd0-4ee8-b99c-781d08c18838@intel.com/T/#t
>---
> crypto/async_tx/async_memcpy.c      | 4 ++--
> crypto/async_tx/async_pq.c          | 8 ++++----
> crypto/async_tx/async_raid6_recov.c | 8 ++++----
> crypto/async_tx/async_xor.c         | 8 ++++----
> drivers/dma/dmaengine.c             | 4 ++--
> drivers/dma/dmatest.c               | 2 +-
> drivers/dma/mv_xor.c                | 4 ++--
> drivers/ntb/ntb_transport.c         | 4 ++--
> drivers/ntb/test/ntb_perf.c         | 2 +-
> include/linux/dmaengine.h           | 4 ++--
> 10 files changed, 24 insertions(+), 24 deletions(-)
>


Reviewed-by: Peng Fan <peng.fan@nxp.com>

  reply	other threads:[~2026-10-15  2:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-14 19:03 [PATCH v3 1/2] dmaengine: change dmaengine_get_unmap_data() first arg to dma_chan Frank.Li
2026-10-15  2:55 ` Peng Fan [this message]
2026-10-15  3:09   ` Frank Li

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=atBAnIzA3X6PgB+6@shlinux89 \
    --to=peng.fan@oss.nxp.com \
    --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 \
    --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 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.