From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Frank.Li@oss.nxp.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>,
"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>, "Thorsten Blum" <blum@kernel.org>,
"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: Wed, 4 Nov 2026 22:34:26 +0200 [thread overview]
Message-ID: <auuW0safpswDmp13@ashevche-desk.local> (raw)
In-Reply-To: <7b476c24-3185-49ff-9a72-fbd865dc0d65@kernel.org>
On Wed, Nov 04, 2026 at 06:51:10PM +0100, Krzysztof Kozlowski wrote:
> On 02/11/2026 17:45, Frank.Li@oss.nxp.com wrote:
> > diff --git a/drivers/crypto/atmel-aes.c b/drivers/crypto/atmel-aes.c
> > index 84392411b98d8..49f1bf19747d8 100644
> > --- a/drivers/crypto/atmel-aes.c
> > +++ b/drivers/crypto/atmel-aes.c
> > @@ -824,8 +824,7 @@ static int atmel_aes_dma_transfer_start(struct atmel_aes_dev *dd,
> > if (!desc)
> > return -ENOMEM;
> >
> > - desc->callback = callback;
> > - desc->callback_param = dd;
> > + dmaengine_desc_set_callback(desc, callback, NULL, dd);
> > dmaengine_submit(desc);
> > dma_async_issue_pending(dma->chan);
> >
>
> Apparently reviewing only a few lines of entire patch is still reviewing:
> https://lore.kernel.org/all/9e39502a-dd17-4fa2-98a3-9019523cb5e8@kernel.org/
>
> Therefore:
> Reviewed-by: Krzysztof Kozlowski <krzk@kernel.org>
Yep, in a form of
Reviewed-by: Krzysztof Kozlowski <krzk@kernel.org> # atmel-aes
or something that makes it clear what has been reviewed.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-11-04 20:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 16:45 Frank.Li
2026-11-02 17:34 ` Thorsten Blum
2026-11-03 12:28 ` Bartosz Golaszewski
2026-11-03 16:21 ` T, Pratham
2026-11-04 17:51 ` Krzysztof Kozlowski
2026-11-04 20:34 ` Andy Shevchenko [this message]
2026-11-05 8:16 ` Bartosz Golaszewski
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=auuW0safpswDmp13@ashevche-desk.local \
--to=andriy.shevchenko@linux.intel.com \
--cc=Frank.Li@nxp.com \
--cc=Frank.Li@oss.nxp.com \
--cc=alexandre.belloni@bootlin.com \
--cc=alexandre.torgue@foss.st.com \
--cc=blum@kernel.org \
--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=krzk@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-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®