From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Rami Rosen <ramirose@gmail.com>, dev@dpdk.org
Cc: konstantin.ananyev@intel.com, arybchenko@solarflare.com,
stable@dpdk.org, Thomas Monjalon <thomas@monjalon.net>,
John McNamara <john.mcnamara@intel.com>
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH] ethdev: fix a typo
Date: Mon, 25 Mar 2019 14:16:20 +0000 [thread overview]
Message-ID: <4ad956d8-597e-93f8-8318-f5a45c1cf8f1@intel.com> (raw)
Message-ID: <20190325141620.8pPFg9R_AiXPVUYpIhFksKtaufmsEv5w2ISpZeJYeOg@z> (raw)
In-Reply-To: <20190322151753.6345-1-ramirose@gmail.com>
On 3/22/2019 3:17 PM, Rami Rosen wrote:
> This patch fixes a trivial typo in rte_ethdev.h.
> retieve=>retrieve
>
> Fixes: 80a1deb4c77a ("ethdev: add API to retrieve queue information")
> Cc: stable@dpdk.org
>
> Signed-off-by: Rami Rosen <ramirose@gmail.com>
Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
Applied to dpdk-next-net/master, thanks.
It is great to have these fixes, but I wonder if there is a way to get them
fixed as a bunch, can running a spell check utility on the DPDK and fix all
existing typos in one go help? Any idea?
cc'ed John & Thomas,
Does it make sense to run something periodical, like before each release, run
spellcheck and fix the typos for whole code?
Thanks,
ferruh
next prev parent reply other threads:[~2019-03-25 14:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-22 15:17 [dpdk-dev] " Rami Rosen
2019-03-22 15:17 ` Rami Rosen
2019-03-25 14:16 ` Ferruh Yigit [this message]
2019-03-25 14:16 ` [dpdk-dev] [dpdk-stable] " Ferruh Yigit
2019-03-25 14:29 ` Thomas Monjalon
2019-03-25 14:29 ` 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=4ad956d8-597e-93f8-8318-f5a45c1cf8f1@intel.com \
--to=ferruh.yigit@intel.com \
--cc=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=konstantin.ananyev@intel.com \
--cc=ramirose@gmail.com \
--cc=stable@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 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).