From: Bin Zheng <zhengbin.89740@bytedance.com>
To: dev@dpdk.org
Cc: haiyue.wang@intel.com, liangma@liangbit.com,
Bin Zheng <zhengbin.89740@bytedance.com>
Subject: [PATCH v2 2/2] net/ixgbe: fix spelling mistakes
Date: Thu, 2 Dec 2021 17:20:01 +0800 [thread overview]
Message-ID: <20211202092001.1830481-2-zhengbin.89740@bytedance.com> (raw)
In-Reply-To: <20211202092001.1830481-1-zhengbin.89740@bytedance.com>
fix comment spelling mistakes
Signed-off-by: Bin Zheng <zhengbin.89740@bytedance.com>
---
drivers/net/ixgbe/ixgbe_rxtx_vec_sse.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/ixgbe/ixgbe_rxtx_vec_sse.c b/drivers/net/ixgbe/ixgbe_rxtx_vec_sse.c
index 5811749b95..4654d0adec 100644
--- a/drivers/net/ixgbe/ixgbe_rxtx_vec_sse.c
+++ b/drivers/net/ixgbe/ixgbe_rxtx_vec_sse.c
@@ -368,7 +368,7 @@ _recv_raw_pkts_vec(struct ixgbe_rx_queue *rxq, struct rte_mbuf **rx_pkts,
* Under the circumstance that `rx_tail` wrap back to zero
* and the advance speed of `rx_tail` is greater than `rxrearm_start`,
* `rx_tail` will catch up with `rxrearm_start` and surpass it.
- * This may cause some mbufs be reused by applicaion.
+ * This may cause some mbufs be reused by application.
*
* So we need to make some restrictions to ensure that
* `rx_tail` will not exceed `rxrearm_start`.
--
2.25.1
next prev parent reply other threads:[~2021-12-02 9:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-02 9:20 [PATCH v2 1/2] net/ixgbe: add vector Rx parameter check Bin Zheng
2021-12-02 9:20 ` Bin Zheng [this message]
2021-12-02 12:53 ` [PATCH v2 2/2] net/ixgbe: fix spelling mistakes Wang, Haiyue
2021-12-10 8:22 ` [PATCH v3] net/ixgbe: add vector Rx parameter check Bin Zheng
2021-12-13 3:02 ` Rong, Leyi
2021-12-14 7:29 ` Wang, Haiyue
2022-01-11 0:31 ` Zhang, Qi Z
2021-12-15 8:07 ` Liang Ma
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=20211202092001.1830481-2-zhengbin.89740@bytedance.com \
--to=zhengbin.89740@bytedance.com \
--cc=dev@dpdk.org \
--cc=haiyue.wang@intel.com \
--cc=liangma@liangbit.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).