[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <6598b080d13e4f08d92899857927200a83f1ddfe.camel@perches.com>
Date: Fri, 14 Jan 2022 18:10:11 -0800
From: Joe Perches <joe@...ches.com>
To: Mimi Zohar <zohar@...ux.ibm.com>,
Austin Kim <austinkernel.kim@...il.com>,
Austin Kim <austindh.kim@...il.com>
Cc: dmitry.kasatkin@...il.com, linux-integrity@...r.kernel.org,
linux-security-module@...r.kernel.org,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] ima: Fix trivial typos in the comments
On Fri, 2022-01-14 at 08:27 -0500, Mimi Zohar wrote:
> Hi Joe,
>
> On Thu, 2022-01-13 at 18:05 -0800, Joe Perches wrote:
> > On Thu, 2022-01-13 at 20:51 -0500, Mimi Zohar wrote:
> > > On Wed, 2022-01-12 at 17:46 +0900, Austin Kim wrote:
> > > > > There are a few minor typos in the comments. Fix these.
> > > It would be really nice if checkpatch.pl would catch spelling mistakes
> > > before the patch was upstreamed.
> >
> > Try ./scripts/checkpatch.pl --strict
>
> "--strict" didn't find the typos in comments, but "--codespell" did.
> Nice!
Right, but it does depend on the particular typo.
checkpatch always uses the scripts/spelling.txt dictionary.
codespell isn't always installed on machines and has to be
enabled with that --codespell option.
Anyway, glad it works for you.
Powered by blists - more mailing lists