All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org, Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [PATCH v4 00/19] Remove repeated words in comments and messages
Date: Sun, 12 Mar 2023 10:41:28 +0100	[thread overview]
Message-ID: <38151852.J2Yia2DhmK@thomas> (raw)
In-Reply-To: <20230222162539.127103-1-stephen@networkplumber.org>

22/02/2023 17:25, Stephen Hemminger:
> This is a cleanup of comments and messages. Done by an ugly
> pcregrep across sources and skipping lots of false positives
> 
> The idea is based of what some maintainers have been doing in netdev.
> 
> Series-acked-by: Bruce Richardson <bruce.richardson@intel.com> 
> 
> v4 - rebase and skip fixing common/sfc_efx/base
> 
> Stephen Hemminger (19):
>   ethdev: reword dev_info_get description.
>   remove repeated word 'to'
>   remove repeated word 'is'
>   remove repeated word 'same'
>   remove repeated word 'on'
>   remove repeated word 'in'
>   remove repeated word 'this'
>   remove repeated word 'only'
>   remove repeated word 'worker'
>   remove repeated word 'or'
>   remove repeated word 'table'
>   remove repeated word 'that'
>   remove repeated word 'override'
>   remove repeated word 'groups'
>   remove repeated word 'page'
>   remove repeated word 'individual'
>   remove repeated word 'expected'
>   remove repeated word 'be'
>   remove repeated word 'all'

Squashed and applied, thanks.




      parent reply	other threads:[~2023-03-12  9:41 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <0220722214106.162640-1-stephen@networkplumber.org>
2023-02-22 16:25 ` [PATCH v4 00/19] Remove repeated words in comments and messages Stephen Hemminger
2023-02-22 16:25   ` [PATCH v4 01/19] ethdev: reword dev_info_get description Stephen Hemminger
2023-02-22 16:25   ` [PATCH v4 02/19] remove repeated word 'to' Stephen Hemminger
2023-02-22 16:28     ` Dumitrescu, Cristian
2023-02-22 16:32     ` Hunt, David
2023-02-22 16:25   ` [PATCH v4 03/19] remove repeated word 'is' Stephen Hemminger
2023-02-22 16:25   ` [PATCH v4 04/19] remove repeated word 'same' Stephen Hemminger
2023-02-22 16:25   ` [PATCH v4 05/19] remove repeated word 'on' Stephen Hemminger
2023-02-22 16:31     ` Hunt, David
2023-02-22 16:25   ` [PATCH v4 06/19] remove repeated word 'in' Stephen Hemminger
2023-02-22 16:44     ` Van Haaren, Harry
2023-02-22 16:25   ` [PATCH v4 07/19] remove repeated word 'this' Stephen Hemminger
2023-02-22 16:25   ` [PATCH v4 08/19] remove repeated word 'only' Stephen Hemminger
2023-02-22 16:25   ` [PATCH v4 09/19] remove repeated word 'worker' Stephen Hemminger
2023-02-22 16:30     ` Hunt, David
2023-02-22 16:25   ` [PATCH v4 10/19] remove repeated word 'or' Stephen Hemminger
2023-02-22 16:25   ` [PATCH v4 11/19] remove repeated word 'table' Stephen Hemminger
2023-02-22 16:25   ` [PATCH v4 12/19] remove repeated word 'that' Stephen Hemminger
2023-02-22 16:25   ` [PATCH v4 13/19] remove repeated word 'override' Stephen Hemminger
2023-02-22 16:25   ` [PATCH v4 14/19] remove repeated word 'groups' Stephen Hemminger
2023-02-22 16:25   ` [PATCH v4 15/19] remove repeated word 'page' Stephen Hemminger
2023-02-22 16:25   ` [PATCH v4 16/19] remove repeated word 'individual' Stephen Hemminger
2023-02-22 16:25   ` [PATCH v4 17/19] remove repeated word 'expected' Stephen Hemminger
2023-02-22 16:25   ` [PATCH v4 18/19] remove repeated word 'be' Stephen Hemminger
2023-02-22 16:25   ` [PATCH v4 19/19] remove repeated word 'all' Stephen Hemminger
2023-03-12  9:41   ` Thomas Monjalon [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=38151852.J2Yia2DhmK@thomas \
    --to=thomas@monjalon.net \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=stephen@networkplumber.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 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.