From: "Van Haaren, Harry" <harry.van.haaren@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: Dongdong Liu <liudongdong3@huawei.com>,
Yisen Zhuang <yisen.zhuang@huawei.com>,
Matan Azrad <matan@nvidia.com>,
"Viacheslav Ovsiienko" <viacheslavo@nvidia.com>,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
"Matz, Olivier" <olivier.matz@6wind.com>
Subject: RE: [PATCH v4 06/19] remove repeated word 'in'
Date: Wed, 22 Feb 2023 16:44:40 +0000 [thread overview]
Message-ID: <BN0PR11MB57128BE437B5CE75705F0668D7AA9@BN0PR11MB5712.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20230222162539.127103-7-stephen@networkplumber.org>
> -----Original Message-----
> From: Stephen Hemminger <stephen@networkplumber.org>
> Sent: Wednesday, February 22, 2023 4:25 PM
> To: dev@dpdk.org
> Cc: Stephen Hemminger <stephen@networkplumber.org>; Van Haaren, Harry
> <harry.van.haaren@intel.com>; Dongdong Liu <liudongdong3@huawei.com>; Yisen
> Zhuang <yisen.zhuang@huawei.com>; Matan Azrad <matan@nvidia.com>;
> Viacheslav Ovsiienko <viacheslavo@nvidia.com>; Andrew Rybchenko
> <andrew.rybchenko@oktetlabs.ru>; Matz, Olivier <olivier.matz@6wind.com>
> Subject: [PATCH v4 06/19] remove repeated word 'in'
Lots of "in" and and one instance of "require" in in the event/sw PMD. Thanks for fixing!
> Found by doing duplicate word scan.
>
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
All patch snippets LGTM:
Acked-by: Harry van Haaren <harry.van.haaren@intel.com>
next prev parent reply other threads:[~2023-02-22 16:44 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 [this message]
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 ` [PATCH v4 00/19] Remove repeated words in comments and messages 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=BN0PR11MB57128BE437B5CE75705F0668D7AA9@BN0PR11MB5712.namprd11.prod.outlook.com \
--to=harry.van.haaren@intel.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=liudongdong3@huawei.com \
--cc=matan@nvidia.com \
--cc=olivier.matz@6wind.com \
--cc=stephen@networkplumber.org \
--cc=viacheslavo@nvidia.com \
--cc=yisen.zhuang@huawei.com \
/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;
as well as URLs for NNTP newsgroup(s).