[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5c7f67b13037d5c95318f3de6f4f34f01c4aca10.camel@perches.com>
Date: Fri, 17 Jun 2022 12:06:04 -0700
From: Joe Perches <joe@...ches.com>
To: "Limonciello, Mario" <Mario.Limonciello@....com>,
Jonathan Corbet <corbet@....net>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Cc: "linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>
Subject: Re: [PATCH 2/2] Documentation: Add a blurb about using
scripts/git-send-email.sh
On Fri, 2022-06-17 at 18:54 +0000, Limonciello, Mario wrote:
> > -----Original Message-----
> > From: Jonathan Corbet <corbet@....net>
[]
> > > diff --git a/Documentation/process/submitting-patches.rst
[]
> > > @@ -225,7 +225,10 @@ Select the recipients for your patch
> > > ------------------------------------
> > >
> > > You should always copy the appropriate subsystem maintainer(s) on any patch
> > > -to code that they maintain; look through the MAINTAINERS file and the
> > > +to code that they maintain. A helper script is available in
> > > +./scripts/git-send-email.sh that can be used with git-send-email to automatically
> > > +findd the appropriate recipients for a patch.
> >
> > Please run a spelling checker on your documentation changes.
> Oh whoops; sorry. I'm a bit surprised ./scripts/checkpatch didn't catch that.
checkpatch (and codespell) relies on a list of common misspellings.
You could add the misspelling to scripts/spelling.txt or maybe
add --codespell to the checkpatch invocation.
But adding --codespell here didn't find that typo either as
the codespell dictionary list doesn't include "findd".
Powered by blists - more mailing lists