All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: <dev@dpdk.org>, Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [PATCH] devtools: fix false positive from checkpatch
Date: Tue, 17 Sep 2024 09:54:46 -0700	[thread overview]
Message-ID: <20240917095446.4665956a@hermes.local> (raw)
In-Reply-To: <ZumkH86HjT9JDr_S@bricha3-mobl1.ger.corp.intel.com>

On Tue, 17 Sep 2024 16:45:35 +0100
Bruce Richardson <bruce.richardson@intel.com> wrote:

> >  # concatenate codespell dictionaries, except GB/US one
> >  for suffix in .txt _code.txt _informal.txt _names.txt _rare.txt _usage.txt ; do
> > @@ -17,6 +21,7 @@ sed '/^..->/d' |
> >  sed '/^uint->/d' |
> >  sed "/^doesn'->/d" |
> >  sed '/^wasn->/d' |
> > +sed '/stdio->/d' |
> >    
> Seems a good idea. However, why use "stdio" alone rather than using the
> full "stdio.h" header name. Do we expect "stdio" to be used much in
> comments or otherwise?
> 
> /Bruce

This script removes entries from the codespell dictionary.
So we are removing this line:
	stdio->studio
Which causes:
WARNING:TYPO_SPELLING: 'stdio' may be misspelled - perhaps 'studio'?

  parent reply	other threads:[~2024-09-17 16:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-17 15:34 [PATCH] devtools: fix false positive from checkpatch Stephen Hemminger
2024-09-17 15:45 ` Bruce Richardson
2024-09-17 15:49   ` Thomas Monjalon
2024-09-17 16:54   ` Stephen Hemminger [this message]
2024-09-17 16:56 ` [PATCH v2] " Stephen Hemminger
2024-11-30 21:36   ` Thomas Monjalon

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=20240917095446.4665956a@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=thomas@monjalon.net \
    /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.