From: Colin Ian King <colin.king@canonical.com>
To: Joe Perches <joe@perches.com>, Jiri Kosina <trivial@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: ACK: [PATCH] spelling.txt: Remove some duplicate entries
Date: Wed, 5 Aug 2020 19:23:40 +0100 [thread overview]
Message-ID: <331cef86-fef3-cdb3-c04d-5457e730e7d0@canonical.com> (raw)
In-Reply-To: <91ea17761845500f161ab343ea6e3415d3564d7b.camel@perches.com>
On 05/08/2020 19:14, Joe Perches wrote:
> Found when Colin King fixed a typo for falied/failed
> and a git grep showed 2 entries in this file.
>
> Signed-off-by: Joe Perches <joe@perches.com>
> ---
>
> scripts/spelling.txt | 4 ----
> 1 file changed, 4 deletions(-)
>
> diff --git a/scripts/spelling.txt b/scripts/spelling.txt
> index f253681e7e2a..b703e4fd51e8 100644
> --- a/scripts/spelling.txt
> +++ b/scripts/spelling.txt
> @@ -596,7 +596,6 @@ extenstion||extension
> extracter||extractor
> faied||failed
> faield||failed
> -falied||failed
> faild||failed
> failded||failed
> failer||failure
> @@ -793,7 +792,6 @@ interrup||interrupt
> interrups||interrupts
> interruptted||interrupted
> interupted||interrupted
> -interupt||interrupt
> intial||initial
> intialisation||initialisation
> intialised||initialised
> @@ -968,7 +966,6 @@ occurd||occurred
> occured||occurred
> occurence||occurrence
> occure||occurred
> -occured||occurred
> occuring||occurring
> offser||offset
> offet||offset
> @@ -1437,7 +1434,6 @@ udpate||update
> uesd||used
> uknown||unknown
> usccess||success
> -usupported||unsupported
> uncommited||uncommitted
> uncompatible||incompatible
> unconditionaly||unconditionally
>
>
Ah, good catch. My bad.
Acked-by: Colin Ian King <colin.king@canonical.com>
prev parent reply other threads:[~2020-08-05 18:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-05 18:14 Joe Perches
2020-08-05 18:23 ` Colin Ian King [this message]
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=331cef86-fef3-cdb3-c04d-5457e730e7d0@canonical.com \
--to=colin.king@canonical.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@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
all inboxes | Powered by JetHome®