From: Thorsten Blum <blum@kernel.org>
To: Frank.Li@oss.nxp.com
Cc: "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>,
"Bartosz Golaszewski" <brgl@kernel.org>,
"Jia Jie Ho" <jiajie.ho@starfivetech.com>,
"William Qiu" <william.qiu@starfivetech.com>,
"Maxime Coquelin" <mcoquelin.stm32@gmail.com>,
"Alexandre Torgue" <alexandre.torgue@foss.st.com>,
"T Pratham" <t-pratham@ti.com>, "Frank Li" <Frank.Li@nxp.com>,
"Pan Chuang" <panchuang@vivo.com>,
"Maxime Méré" <maxime.mere@foss.st.com>,
"open list:CRYPTO API" <linux-crypto@vger.kernel.org>,
"moderated list:ARM/Microchip (AT91) SoC support"
<linux-arm-kernel@lists.infradead.org>,
"open list" <linux-kernel@vger.kernel.org>,
"open list:QUALCOMM CRYPTO DRIVERS"
<linux-arm-msm@vger.kernel.org>,
"moderated list:ARM/STM32 ARCHITECTURE"
<linux-stm32@st-md-mailman.stormreply.com>,
imx@lists.linux.dev, vkoul@kernel.org
Subject: Re: [PATCH 1/1] crypto: use dmaengine_desc_set_callback()
Date: Mon, 2 Nov 2026 18:34:05 +0100 [thread overview]
Message-ID: <aujJjW1ploEzmcZ4@kernel.org> (raw)
In-Reply-To: <20261102164538.3834039-1-Frank.Li@oss.nxp.com>
Hi Frank,
On Mon, Nov 02, 2026 at 11:45:30AM -0500, Frank.Li@oss.nxp.com wrote:
> From: Frank Li <Frank.Li@nxp.com>
>
> Replace open-coded assignments to callback and callback_param fields
> of struct dma_async_tx_descriptor with calls to the
> dmaengine_desc_set_callback() helper across various crypto drivers.
>
> No functional change intended. Prepare make to struct
^^^^^^^ to make?
> dma_async_tx_descriptor private to the DMA engine.
>
> Signed-off-by: Frank Li <Frank.Li@nxp.com>
> ---
> drivers/crypto/atmel-aes.c | 3 +--
> drivers/crypto/atmel-sha.c | 6 ++----
> drivers/crypto/atmel-tdes.c | 3 +--
> drivers/crypto/img-hash.c | 3 +--
> drivers/crypto/omap-aes.c | 8 +++-----
> drivers/crypto/omap-des.c | 5 ++---
> drivers/crypto/omap-sham.c | 3 +--
> drivers/crypto/qce/dma.c | 3 +--
> drivers/crypto/sa2ul.c | 3 +--
> drivers/crypto/starfive/jh7110-aes.c | 3 +--
> drivers/crypto/starfive/jh7110-hash.c | 3 +--
> drivers/crypto/stm32/stm32-cryp.c | 9 +++------
> drivers/crypto/stm32/stm32-hash.c | 3 +--
> drivers/crypto/ti/dthev2-aes.c | 9 +++------
> 14 files changed, 22 insertions(+), 42 deletions(-)
Reviewed-by: Thorsten Blum <blum@kernel.org>
next prev parent reply other threads:[~2026-11-02 17:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 16:45 Frank.Li
2026-11-02 17:34 ` Thorsten Blum [this message]
2026-11-03 12:28 ` Bartosz Golaszewski
2026-11-03 16:21 ` T, Pratham
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=aujJjW1ploEzmcZ4@kernel.org \
--to=blum@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=Frank.Li@oss.nxp.com \
--cc=alexandre.belloni@bootlin.com \
--cc=alexandre.torgue@foss.st.com \
--cc=brgl@kernel.org \
--cc=claudiu.beznea@tuxon.dev \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=imx@lists.linux.dev \
--cc=jiajie.ho@starfivetech.com \
--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-stm32@st-md-mailman.stormreply.com \
--cc=maxime.mere@foss.st.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=nicolas.ferre@microchip.com \
--cc=panchuang@vivo.com \
--cc=t-pratham@ti.com \
--cc=vkoul@kernel.org \
--cc=william.qiu@starfivetech.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®