From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>,
Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>,
Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>
Subject: [PATCH v4 07/19] remove repeated word 'this'
Date: Wed, 22 Feb 2023 08:25:27 -0800 [thread overview]
Message-ID: <20230222162539.127103-8-stephen@networkplumber.org> (raw)
In-Reply-To: <20230222162539.127103-1-stephen@networkplumber.org>
Found by doing duplicate word scan.
Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
---
lib/ring/rte_ring.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/lib/ring/rte_ring.c b/lib/ring/rte_ring.c
index cddaf6b2876f..8ed455043dee 100644
--- a/lib/ring/rte_ring.c
+++ b/lib/ring/rte_ring.c
@@ -280,7 +280,8 @@ rte_ring_create_elem(const char *name, unsigned int esize, unsigned int count,
/* reserve a memory zone for this ring. If we can't get rte_config or
* we are secondary process, the memzone_reserve function will set
- * rte_errno for us appropriately - hence no check in this this function */
+ * rte_errno for us appropriately - hence no check in this function
+ */
mz = rte_memzone_reserve_aligned(mz_name, ring_size, socket_id,
mz_flags, __alignof__(*r));
if (mz != NULL) {
--
2.39.1
next prev parent reply other threads:[~2023-02-22 16:26 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 ` Stephen Hemminger [this message]
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=20230222162539.127103-8-stephen@networkplumber.org \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=honnappa.nagarahalli@arm.com \
--cc=konstantin.v.ananyev@yandex.ru \
/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).