From: Thomas Huth <thuth@redhat.com>
To: "Zhao Liu" <zhao1.liu@linux.intel.com>,
"Michael Tokarev" <mjt@tls.msk.ru>,
"Laurent Vivier" <laurent@vivier.eu>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Darren Kenny" <darren.kenny@oracle.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Alexander Bulekov" <alxndr@bu.edu>,
qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, Zhenyu Wang <zhenyu.z.wang@intel.com>,
Zhao Liu <zhao1.liu@intel.com>, Yongwei Ma <yongwei.ma@intel.com>,
Samuel Tardieu <sam@rfc1149.net>
Subject: Re: [PATCH v3] scripts/checkpatch: Support codespell checking
Date: Thu, 11 Jan 2024 09:52:46 +0100 [thread overview]
Message-ID: <72c3cf5f-29ef-4adf-925d-7d5e36c65b7e@redhat.com> (raw)
In-Reply-To: <20240105083848.267192-1-zhao1.liu@linux.intel.com>
On 05/01/2024 09.38, Zhao Liu wrote:
> From: Zhao Liu <zhao1.liu@intel.com>
>
> Add two spelling check options (--codespell and --codespellfile) to
> enhance spelling check through dictionary, which copied the Linux
> kernel's implementation in checkpatch.pl.
>
> This check uses the dictionary at "/usr/share/codespell/dictionary.txt"
> by default, if there is no dictionary specified under this path, it
> will look for the dictionary of python3's codespell (This requires user
> to add python3's path in environment variable $PATH, and to install
> codespell by "pip install codespell").
>
> Tested-by: Yongwei Ma <yongwei.ma@intel.com>
> Tested-by: Samuel Tardieu <sam@rfc1149.net>
> Signed-off-by: Zhao Liu <zhao1.liu@intel.com>
Tested-by: Thomas Huth <thuth@redhat.com>
Thanks, I'll add it to my next pull request.
prev parent reply other threads:[~2024-01-11 8:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-05 8:38 [PATCH v3] scripts/checkpatch: Support codespell checking Zhao Liu
2024-01-11 8:52 ` Thomas Huth [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=72c3cf5f-29ef-4adf-925d-7d5e36c65b7e@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=alxndr@bu.edu \
--cc=darren.kenny@oracle.com \
--cc=laurent@vivier.eu \
--cc=mjt@tls.msk.ru \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=sam@rfc1149.net \
--cc=yongwei.ma@intel.com \
--cc=zhao1.liu@intel.com \
--cc=zhao1.liu@linux.intel.com \
--cc=zhenyu.z.wang@intel.com \
/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).