crypto: fix spelling errors in comments
PATCH v2 1/1 crypto: fix spelling errors in comments
Fix several spelling mistakes in comments across the following files:
- crypto/tea.c: Correct "alogrithms" to "algorithms"
- crypto/lrw.c: Correct "mutliple" to "multiple"
- crypto/drbg.c: Correct "additonal" to "additional"
No functional change.
Signed-off-by Sun Chaobo <[email protected]>
--- crypto/drbg.c | 2 +- crypto/lrw.c | 2 +- crypto/tea.c | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-)
crypto/drbg.c +1 -1
@@ -1780,7 +1780,7 @@ static inline int __init drbg_healthcheck_sanity(void) max_addtllen =drbg_max_addtl (drbg); max_request_bytes =drbg_max_request_bytes (drbg);drbg_string_fill (&addtl, buf, max_addtllen +1 ); -/* overflow addtllen with additonal info string */ +/* overflow addtllen with additional info string */ len =drbg_generate (drbg, buf,OUTBUFLEN , &addtl);BUG_ON (0 < len);/* overflow max_bits */
crypto/lrw.c +1 -1
@@ -134,7 +134,7 @@ static int lrw_next_index(u32 *counter)/* * 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 lrw_next_index() calls again. */ static int lrw_xor_tweak (struct skcipher_request *req,bool second_pass)
crypto/tea.c +1 -1
@@ -2,7 +2,7 @@/* * Cryptographic API. * -* TEA, XTEA, and XETA crypto alogrithms +* TEA, XTEA, and XETA crypto algorithms * * The TEA and Xtended TEA algorithms were developed by David Wheeler * and Roger Needham at the Computer Laboratory of Cambridge University.
Signature · 11 lines
2.53.0
Changes since v1:
- Fixed multiple typos in the commit message description.
1. Corrected the spelling of the target word "algorithms" (added missing 's').
2. Fixed a typo in the quoted original error string (the original code had
"alogrithms", but I accidentally mistyped it again in the v1 log).
Both are now accurately represented.
- The actual code diff remains unchanged from v1; the source code fixes
were already correct in v1.
- No functional changes.