From: "Paul Louvel" <paul.louvel@bootlin.com>
To: "Paul Louvel" <paul.louvel@bootlin.com>,
"Goetz Goerisch" <ggoerisch@gmail.com>
Cc: <herve.codina@bootlin.com>, <miquel.raynal@bootlin.com>,
<stable@vger.kernel.org>, <thomas.petazzoni@bootlin.com>,
"Herbert Xu" <herbert@gondor.apana.org.au>,
<linux-crypto@vger.kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Sasha Levin" <sashal@kernel.org>
Subject: Re: [PATCH] crypto: talitos - fix rename first/last to first_desc/last_desc
Date: Thu, 21 May 2026 12:20:18 +0200 [thread overview]
Message-ID: <DIOA24QU02W5.2RSVK05RE7BJK@bootlin.com> (raw)
In-Reply-To: <DIO9YUHO5VGT.3BLGH04NVJNHP@bootlin.com>
On Thu May 21, 2026 at 12:16 PM CEST, Paul Louvel wrote:
> On Wed May 20, 2026 at 6:58 PM CEST, Goetz Goerisch wrote:
>> Hi,
>>
>> Commit a1b80018b8cec27fc06a8b04a7f8b5f6cfe86eae
>> was backported to 6.6.y with a866e2b1c65edaee2e1bb1024ee2c761ced335f8
>> It renames last to last_desc but misses one occurrence which leads to compile errors on mpc85xx
>
> Hi Goetz,
>
> Thank you for the patch. I did not catch that since I worked on a mainline tree,
> and that specific line was removed in 9826d1d6ed5f ("crypto: talitos - stop
> using crypto_ahash::init"), which was not backported into the stable tree.
>
>> drivers/crypto/talitos.c: In function 'ahash_digest':
>> drivers/crypto/talitos.c:2204:16: error: 'struct talitos_ahash_req_ctx' has no member named 'last'
>> 2204 | req_ctx->last = 1;
>> | ^~4
>>
>> Fixes: a866e2b1c65e ("crypto: talitos - rename first/last to first_desc/last_desc")
>> Signed-off-by: Goetz Goerisch <ggoerisch@gmail.com>
>> ---
>> drivers/crypto/talitos.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/crypto/talitos.c b/drivers/crypto/talitos.c
>> index 347483f6fc5d..ed160c591346 100644
>> --- a/drivers/crypto/talitos.c
>> +++ b/drivers/crypto/talitos.c
>> @@ -2201,7 +2201,7 @@ static int ahash_digest(struct ahash_request *areq)
>> struct crypto_ahash *ahash = crypto_ahash_reqtfm(areq);
>>
>> ahash->init(areq);
>> - req_ctx->last = 1;
>> + req_ctx->last_desc = 1;
>
> Instead of renaming req_ctx->last, commit 9826d1d6ed5f8 ("crypto: talitos - stop
> using crypto_ahash::init") should be applied. Ideally before commit
> 655ef638a2bc ("crypto: talitos - fix SEC1 32k ahash request limitation") to
> avoid any compilation breakage and ensure correctness of the code.
Small correction:
Ideally before commit 00463d5f864a ("crypto: talitos - fix SEC1 32k ahash
request limitation") to avoid any compilation breakage and ensure correctness of
the code.
>
>>
>> return ahash_process_req(areq, areq->nbytes);
>> }
>
> Paul.
--
Paul Louvel, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2026-05-21 10:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <142603430.61540.1779296295550@app.mailbox.org>
2026-05-21 10:16 ` [PATCH] crypto: talitos - fix rename first/last to first_desc/last_desc Paul Louvel
2026-05-21 10:20 ` Paul Louvel [this message]
2026-05-21 15:25 ` Goetz Goerisch
2026-05-22 5:12 ` Greg Kroah-Hartman
2026-05-23 15:10 ` [PATCH 0/5] " Goetz Goerisch
2026-05-23 15:10 ` [PATCH 1/5] Revert "crypto: talitos - rename first/last to first_desc/last_desc" Goetz Goerisch
2026-05-23 15:10 ` [PATCH 2/5] Revert "crypto: talitos - fix SEC1 32k ahash request limitation" Goetz Goerisch
2026-05-23 15:10 ` [PATCH 3/5] crypto: talitos - stop using crypto_ahash::init Goetz Goerisch
2026-05-23 15:10 ` [PATCH 4/5] crypto: talitos - fix SEC1 32k ahash request limitation Goetz Goerisch
2026-05-23 15:10 ` [PATCH 5/5] crypto: talitos - rename first/last to first_desc/last_desc Goetz Goerisch
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=DIOA24QU02W5.2RSVK05RE7BJK@bootlin.com \
--to=paul.louvel@bootlin.com \
--cc=ggoerisch@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=herbert@gondor.apana.org.au \
--cc=herve.codina@bootlin.com \
--cc=linux-crypto@vger.kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=thomas.petazzoni@bootlin.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