From: Sean Christopherson <seanjc@google.com>
To: "Colin King (gmail)" <colin.i.king@gmail.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Shuah Khan <shuah@kernel.org>,
kvm@vger.kernel.org, linux-kselftest@vger.kernel.org,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][next] KVM: selftests: Fix spelling mistake "probabalistic" -> "probabilistic"
Date: Fri, 2 Dec 2022 18:31:05 +0000 [thread overview]
Message-ID: <Y4pEaaQsnDWEOxjH@google.com> (raw)
In-Reply-To: <10445a4d-0175-3e5e-aa74-9d232737a7c2@gmail.com>
On Fri, Dec 02, 2022, Colin King (gmail) wrote:
> On 02/12/2022 17:21, Sean Christopherson wrote:
> > On Thu, Dec 01, 2022, Colin Ian King wrote:
> > > There is a spelling mistake in some help text. Fix it.
> >
> > I assume you have a script/tool of some form to do spell checking? If so, can
> > you point me at it? I'd love to incorporate something like that into my workflow.
>
> https://github.com/ColinIanKing/kernelscan
>
> It needs an appropriate dictionary to be installed. It's very fast (but
> sometimes makes mistakes, I need to fix those!).
>
> ./kernelscan -k src_directory > mistakes.txt
Ah, it's specifically checking messages to avoid false postives on code and whatnot.
Neat!
> I normally run this across the entire kernel git repo on a daily basis, and
> diff the new results with the previous results using meld and figure out
> what needs to be fixed.
>
> You may be better off with using codespell
Heh, my kind of nitpicking people :-)
MSDOS->MS-DOS
Thanks a ton, that's exactly what I was looking for!
next prev parent reply other threads:[~2022-12-02 18:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-01 9:13 [PATCH][next] KVM: selftests: Fix spelling mistake "probabalistic" -> "probabilistic" Colin Ian King
2022-12-02 17:21 ` Sean Christopherson
2022-12-02 17:43 ` Colin King (gmail)
2022-12-02 18:31 ` Sean Christopherson [this message]
2022-12-02 18:57 ` Sean Christopherson
2022-12-02 20:24 ` Colin King (gmail)
2022-12-02 18:24 ` Paolo Bonzini
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=Y4pEaaQsnDWEOxjH@google.com \
--to=seanjc@google.com \
--cc=colin.i.king@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=shuah@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.