From 46d11fc6e753e0c8d2b2e43c2a57918f656fa99a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Tobias=20Frauenschl=C3=A4ger?= Date: Wed, 21 Oct 2026 10:44:32 +0200 Subject: [PATCH] Drop a stale note from the generic SETKEY claim comment The comment on a successful WC_SETKEY_AES claim said rounds stays 0 because there is no software key schedule. A callback may now build one and set rounds, so the comment is cut to the line the ARM32 and PPC copies use. --- wolfcrypt/src/aes.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/wolfcrypt/src/aes.c b/wolfcrypt/src/aes.c index c8b30b1c94..b4cf8e93a9 100644 --- a/wolfcrypt/src/aes.c +++ b/wolfcrypt/src/aes.c @@ -6185,9 +6185,7 @@ static void AesSetKey_C(Aes* aes, const byte* key, word32 keySz, int dir) (iv != NULL) ? WC_AES_BLOCK_SIZE : 0, dir); if (cbRet != WC_NO_ERR_TRACE(CRYPTOCB_UNAVAILABLE)) { if (cbRet == 0) { - /* Callback succeeded - the device owns the key. rounds is - * left at 0: there is no software key schedule, and the - * XTS entry points use that to reject the context. */ + /* Callback succeeded - the device owns the key. */ aes->keylen = (int)keylen; *devOwned = 1; if (iv != NULL)