public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: SeongJae Park <sj@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: SeongJae Park <sj@kernel.org>,
	akpm@linux-foundation.org, colin.i.king@gmail.com,
	dfustini@baylibre.com, linux-kernel@vger.kernel.org,
	joe@perches.com
Subject: Re: [PATCH] scripts/spelling: add a few more typos
Date: Tue,  3 Jan 2023 18:09:59 +0000	[thread overview]
Message-ID: <20230103180959.129697-1-sj@kernel.org> (raw)
In-Reply-To: <7247ac21-f06d-74bc-e9ad-34930ec6d0a4@infradead.org>

Hi Randy,

On Tue, 3 Jan 2023 10:04:43 -0800 Randy Dunlap <rdunlap@infradead.org> wrote:

> Hi--
> 
> On 1/3/23 09:59, SeongJae Park wrote:
> > Add a few more typos that found from real patches[1,2] to 'spelling'
> > file.
> > 
> > [1] https://lore.kernel.org/linux-mm/4bc4ab74-3ccd-f892-b387-d48451463d3c@huawei.com/
> > [2] https://lore.kernel.org/damon/20221228174621.34868-1-sj@kernel.org/
> > 
> > Signed-off-by: SeongJae Park <sj@kernel.org>
> > ---
> >  scripts/spelling.txt | 4 ++++
> >  1 file changed, 4 insertions(+)
> > 
> > diff --git a/scripts/spelling.txt b/scripts/spelling.txt
> > index ded8bcfc0247..64bddbf7425b 100644
> > --- a/scripts/spelling.txt
> > +++ b/scripts/spelling.txt
> > @@ -411,6 +411,7 @@ contruction||construction
> >  contry||country
> >  conuntry||country
> >  convertion||conversion
> > +covert||convert
> 
> "covert" is a real, valid word. Is it always incorrect when used in kernel
> source or documentation?

You're right.  I will drop this in the next spin.


Thanks,
SJ

> 
> thanks.
> 
> -- 
> ~Randy

  reply	other threads:[~2023-01-03 18:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-03 17:59 [PATCH] scripts/spelling: add a few more typos SeongJae Park
2023-01-03 18:04 ` Randy Dunlap
2023-01-03 18:09   ` SeongJae Park [this message]
2023-01-03 18:07 ` Joe Perches
2023-01-03 18:10   ` SeongJae Park

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=20230103180959.129697-1-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=colin.i.king@gmail.com \
    --cc=dfustini@baylibre.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.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