mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Frank.Li@oss.nxp.com
Cc: Richard Weinberger <richard@nod.at>,
	 Vignesh Raghavendra <vigneshr@ti.com>,
	 Frank Li <Frank.Li@nxp.com>,
	 Alok Tiwari <alok.a.tiwari@oracle.com>,
	 Runyu Xiao <runyu.xiao@seu.edu.cn>,
	 Chen Ni <nichen@iscas.ac.cn>,
	 Kees Cook <kees+treewide@kernel.org>,
	 Hemanth Selam <hemanth.selam@gmail.com>,
	 linux-mtd@lists.infradead.org (open list:CADENCE NAND DRIVER),
	 linux-kernel@vger.kernel.org (open list),
	imx@lists.linux.dev
Subject: Re: [PATCH 1/1] mtd: nand: raw: use dmaengine accessor API functions
Date: Tue, 17 Nov 2026 15:13:25 +0100	[thread overview]
Message-ID: <87bj7nlf5m.fsf@bootlin.com> (raw)
In-Reply-To: <20261111202502.3860647-1-Frank.Li@oss.nxp.com> (Frank Li's message of "Wed, 11 Nov 2026 15:24:45 -0500")

On 11/11/2026 at 15:24:45 -05, Frank.Li@oss.nxp.com wrote:

> From: Frank Li <Frank.Li@nxp.com>
>
> Use dmaengine_get_dma_device() instead of directly accessing chan->device
> and use dmaengine_prep_dma_memcpy() instead of calling the function pointer
> directly. This follows the dmaengine API convention of using accessor
> helpers to decouple drivers from internal dmaengine structures.
>
> Affects cadence-nand-controller and fsmc_nand drivers.
>
> No functional change and prepare to move struct dma_device to private.
>
> Signed-off-by: Frank Li <Frank.Li@nxp.com>

I will fix the subject when applying (nand: raw: -> rawnand:)

Thanks,
Miquèl

  reply	other threads:[~2026-11-17 14:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-11 20:24 Frank.Li
2026-11-17 14:13 ` Miquel Raynal [this message]
2026-11-17 14:23 ` Miquel Raynal

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=87bj7nlf5m.fsf@bootlin.com \
    --to=miquel.raynal@bootlin.com \
    --cc=Frank.Li@nxp.com \
    --cc=Frank.Li@oss.nxp.com \
    --cc=alok.a.tiwari@oracle.com \
    --cc=hemanth.selam@gmail.com \
    --cc=imx@lists.linux.dev \
    --cc=kees+treewide@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=nichen@iscas.ac.cn \
    --cc=richard@nod.at \
    --cc=runyu.xiao@seu.edu.cn \
    --cc=vigneshr@ti.com \
    /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

all inboxes | Powered by JetHome®