DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: "Stephen Hemminger" <stephen@networkplumber.org>,
	"Niklas Söderlund" <niklas.soderlund@corigine.com>,
	"Chaoyong He" <chaoyong.he@corigine.com>
Subject: [PATCH v4 12/19] remove repeated word 'that'
Date: Wed, 22 Feb 2023 08:25:32 -0800	[thread overview]
Message-ID: <20230222162539.127103-13-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>
Reviewed-by: Niklas Söderlund <niklas.soderlund@corigine.com>
---
 drivers/net/nfp/nfp_ctrl.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/net/nfp/nfp_ctrl.h b/drivers/net/nfp/nfp_ctrl.h
index 1069ff948555..2269925b74cf 100644
--- a/drivers/net/nfp/nfp_ctrl.h
+++ b/drivers/net/nfp/nfp_ctrl.h
@@ -196,7 +196,7 @@
  * Reuse spare address to contain the offset from the start of
  * the host buffer where the first byte of the received frame
  * will land.  Any metadata will come prior to that offset.  If the
- * value in this field is 0, it means that that the metadata will
+ * value in this field is 0, it means that the metadata will
  * always land starting at the first byte of the host buffer and
  * packet data will immediately follow the metadata.  As always,
  * the RX descriptor indicates the presence or absence of metadata
-- 
2.39.1


  parent reply	other threads:[~2023-02-22 16:27 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   ` [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   ` Stephen Hemminger [this message]
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-13-stephen@networkplumber.org \
    --to=stephen@networkplumber.org \
    --cc=chaoyong.he@corigine.com \
    --cc=dev@dpdk.org \
    --cc=niklas.soderlund@corigine.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).