From: Kevin Traynor <ktraynor@redhat.com>
To: Thomas Monjalon <thomas@monjalon.net>, Josh Soref <jsoref@gmail.com>
Cc: dev@dpdk.org, Bruce Richardson <bruce.richardson@intel.com>,
Ferruh Yigit <ferruh.yigit@intel.com>,
David Marchand <david.marchand@redhat.com>,
Luca Boccassi <bluca@debian.org>,
Christian Ehrhardt <christian.ehrhardt@canonical.com>,
"Xueming(Steven) Li" <xuemingl@nvidia.com>
Subject: Re: [PATCH v2] Spelling comments/text
Date: Tue, 11 Jan 2022 14:00:48 +0000 [thread overview]
Message-ID: <fa06d406-0ac2-614e-a3f1-1a0bad07776c@redhat.com> (raw)
In-Reply-To: <2808677.e9J7NaK4W3@thomas>
On 11/01/2022 10:51, Thomas Monjalon wrote:
> 06/01/2022 17:46, Thomas Monjalon:
>> 29/11/2021 17:08, Josh Soref:
>>> - * external phy devices registred through kerenl apis
>>> + * external phy devices registred through kernel apis
>>
>> another spelling to fix:
>> "registred"
>> and while at it, "apis" should be "APIs"
>>
>> - * When set to zero, simple forwaring path is eanbled.
>> + * When set to zero, simple forwaring path is enabled.
>>
>> another one:
>> "forwaring"
>>
>> If I see nothing else, I'll fix and merge.
>
> I've found more to fix.
> Given the size of the patch, I did the fixes directly and added my Signed-off.
>
> Applied, thanks.
>
> The git log became:
>
> fix spelling in comments and strings
>
> The tool comes from https://github.com/jsoref
>
> Signed-off-by: Josh Soref <jsoref@gmail.com>
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
>
>
>
Not explicitly requested, but I think we can take whatever applies on
stable branches too - at least for 21.11 where it applies cleanly.
next prev parent reply other threads:[~2022-01-11 14:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-26 19:58 [PATCH] Spelling Josh Soref
2021-11-29 12:49 ` Ferruh Yigit
2021-11-29 13:59 ` Bruce Richardson
2021-11-29 14:02 ` Thomas Monjalon
2021-11-29 18:11 ` Ajit Khaparde
2021-11-29 14:03 ` Ferruh Yigit
2021-11-29 14:12 ` Josh Soref
2021-11-29 14:47 ` Bruce Richardson
2021-11-29 14:52 ` Ferruh Yigit
2021-11-29 16:08 ` [PATCH v2] Spelling comments/text Josh Soref
2022-01-06 16:46 ` Thomas Monjalon
2022-01-11 10:51 ` Thomas Monjalon
2022-01-11 14:00 ` Kevin Traynor [this message]
2022-01-11 14:23 ` Thomas Monjalon
2022-01-06 16:52 ` Thomas Monjalon
2022-01-07 11:23 ` Bruce Richardson
2022-01-07 14:58 ` Thomas Monjalon
2022-01-07 15:04 ` Josh Soref
2022-01-07 15:28 ` Bruce Richardson
2022-01-07 16:27 ` Morten Brørup
2022-01-07 16:37 ` Bruce Richardson
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=fa06d406-0ac2-614e-a3f1-1a0bad07776c@redhat.com \
--to=ktraynor@redhat.com \
--cc=bluca@debian.org \
--cc=bruce.richardson@intel.com \
--cc=christian.ehrhardt@canonical.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jsoref@gmail.com \
--cc=thomas@monjalon.net \
--cc=xuemingl@nvidia.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).