From: Sven Eckelmann <sven@narfation.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
Colin King <colin.king@canonical.com>,
Sven Eckelmann <sven@narfation.org>
Subject: scripts/spelling.txt: Fix "mistake" version of "synchronization"
Date: Sun, 26 Sep 2021 08:55:29 +0200 [thread overview]
Message-ID: <20210926065529.6880-1-sven@narfation.org> (raw)
If both "mistake" version and "correction" version are the same, a warning
message is created by checkpatch which is impossible to fix. But it was
noticed that Colan Ian King created a commit e6c0a0889b80 ("ALSA: aloop:
Fix spelling mistake "synchronization" -> "synchronization"") which
suggests that this spelling mistake was fixed by replacing the word
"synchronization" with itself. But the actual diff shows that the mistake
in the code was "sychronization". It is rather likely that the "mistake"
in spelling.txt should have been the latter.
Fixes: 2e74c9433ba8 ("scripts/spelling.txt: add more spellings to spelling.txt")
Signed-off-by: Sven Eckelmann <sven@narfation.org>
---
This was already reported last week in https://lore.kernel.org/all/1930750.yhyOXdeGKK@sven-l14/
diff --git a/scripts/spelling.txt b/scripts/spelling.txt
index fd8f07317b8e1c572e1e0f6bb4f9e01dff96c17c..acf6ea71129921ad77a201d13761382ee032483e 100644
--- a/scripts/spelling.txt
+++ b/scripts/spelling.txt
@@ -1450,7 +1450,7 @@ syfs||sysfs
symetric||symmetric
synax||syntax
synchonized||synchronized
-synchronization||synchronization
+sychronization||synchronization
synchronuously||synchronously
syncronize||synchronize
syncronized||synchronized
next reply other threads:[~2021-09-26 6:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-26 6:55 Sven Eckelmann [this message]
2021-09-26 11:52 ` scripts/spelling.txt: Fix "mistake" version of "synchronization" Colin Ian King
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=20210926065529.6880-1-sven@narfation.org \
--to=sven@narfation.org \
--cc=akpm@linux-foundation.org \
--cc=colin.king@canonical.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).