From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Josh Soref <jsoref@gmail.com>
Cc: Josh Soref <jsoref@users.noreply.github.com>, <dev@dpdk.org>,
"David Marchand" <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [PATCH] Spelling
Date: Mon, 29 Nov 2021 12:49:56 +0000 [thread overview]
Message-ID: <737b8856-a247-3709-ad4c-a074d4547c86@intel.com> (raw)
In-Reply-To: <20211126195851.50167-1-jsoref@users.noreply.github.com>
On 11/26/2021 7:58 PM, Josh Soref wrote:
> diff --git a/app/test-eventdev/test_order_common.c b/app/test-eventdev/test_order_common.c
> index ff7813f9..603e7c91 100644
> --- a/app/test-eventdev/test_order_common.c
> +++ b/app/test-eventdev/test_order_common.c
> @@ -253,7 +253,7 @@ void
> order_opt_dump(struct evt_options *opt)
> {
> evt_dump_producer_lcores(opt);
> - evt_dump("nb_wrker_lcores", "%d", evt_nr_active_lcores(opt->wlcores));
> + evt_dump("nb_worker_lcores", "%d", evt_nr_active_lcores(opt->wlcores));
Hi Josh, Thanks for the patch.
The typo fixes for comments and logs are more straightforward, but I have
mixed feeling about the variable / macro typo fixes, let's see what others
think.
And I think we should get this patch either one of the first patch or last
patch to prevent conflict with other patches.
next prev parent reply other threads:[~2021-11-29 12:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-26 19:58 Josh Soref
2021-11-29 12:49 ` Ferruh Yigit [this message]
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
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=737b8856-a247-3709-ad4c-a074d4547c86@intel.com \
--to=ferruh.yigit@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=jsoref@gmail.com \
--cc=jsoref@users.noreply.github.com \
--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 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).