From: Sun Chaobo <suncoding913@gmail.com>
To: herbert@gondor.apana.org.au
Cc: linux-crypto@vger.kernel.org, Sun Chaobo <suncoding913@gmail.com>
Subject: [PATCH] crypto: fix spelling errors in comments
Date: Tue, 24 Feb 2026 11:37:56 +0800 [thread overview]
Message-ID: <20260224033756.78693-1-suncoding913@gmail.com> (raw)
Fix several spelling mistakes in comments across the following files:
- crypto/tcrypt.c: Correct "intentionaly" to "intentionally"
- crypto/xts.c: Correct "mutliple" to "multiple"
No functional change.
Signed-off-by: Sun Chaobo <suncoding913@gmail.com>
---
crypto/tcrypt.c | 2 +-
crypto/xts.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/crypto/tcrypt.c b/crypto/tcrypt.c
index aded37546..6374c86a1 100644
--- a/crypto/tcrypt.c
+++ b/crypto/tcrypt.c
@@ -2817,7 +2817,7 @@ static int __init tcrypt_mod_init(void)
pr_debug("all tests passed\n");
}
- /* We intentionaly return -EAGAIN to prevent keeping the module,
+ /* We intentionally return -EAGAIN to prevent keeping the module,
* unless we're running in fips mode. It does all its work from
* init() and doesn't offer any runtime functionality, but in
* the fips case, checking for a successful load is helpful.
diff --git a/crypto/xts.c b/crypto/xts.c
index 3da8f5e05..ad97c8091 100644
--- a/crypto/xts.c
+++ b/crypto/xts.c
@@ -76,7 +76,7 @@ static int xts_setkey(struct crypto_skcipher *parent, const u8 *key,
/*
* We compute the tweak masks twice (both before and after the ECB encryption or
* decryption) to avoid having to allocate a temporary buffer and/or make
- * mutliple calls to the 'ecb(..)' instance, which usually would be slower than
+ * multiple calls to the 'ecb(..)' instance, which usually would be slower than
* just doing the gf128mul_x_ble() calls again.
*/
static int xts_xor_tweak(struct skcipher_request *req, bool second_pass,
--
2.53.0
next reply other threads:[~2026-02-24 3:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 3:37 Sun Chaobo [this message]
2026-03-07 4:55 ` [PATCH] crypto: fix spelling errors in comments Herbert Xu
-- strict thread matches above, loose matches on Subject: below --
2026-02-23 13:28 Sun Chaobo
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=20260224033756.78693-1-suncoding913@gmail.com \
--to=suncoding913@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.