From: "Min Hu (Connor)" <humin29@huawei.com>
To: <dev@dpdk.org>
Cc: <ferruh.yigit@intel.com>
Subject: [dpdk-dev] [PATCH 5/5] doc: fix Rx burst function doc
Date: Tue, 20 Apr 2021 16:59:52 +0800 [thread overview]
Message-ID: <1618909192-17431-6-git-send-email-humin29@huawei.com> (raw)
In-Reply-To: <1618909192-17431-1-git-send-email-humin29@huawei.com>
The patch 'net/hns3: rename Rx burst function' changed `simple'
Rx function name from 'scalar' to 'scalar simple', but doc
ignored that.
This patch fixed it.
Fixes: aa5baf47e1a3 ("net/hns3: rename Rx burst function")
Signed-off-by: Min Hu (Connor) <humin29@huawei.com>
---
doc/guides/nics/hns3.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/guides/nics/hns3.rst b/doc/guides/nics/hns3.rst
index fa45721..52d6718 100644
--- a/doc/guides/nics/hns3.rst
+++ b/doc/guides/nics/hns3.rst
@@ -59,7 +59,7 @@ Runtime Config Options
``sve``, if supported use the ``sve`` Rx function which indicates the
sve algorithm.
``simple``, if supported use the ``simple`` Rx function which indicates
- the scalar algorithm.
+ the scalar simple algorithm.
``common``, if supported use the ``common`` Rx function which indicates
the scalar scattered algorithm.
--
2.7.4
next prev parent reply other threads:[~2021-04-20 9:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-20 8:59 [dpdk-dev] [PATCH 0/5] fixes for hns3 PMD Min Hu (Connor)
2021-04-20 8:59 ` [dpdk-dev] [PATCH 1/5] net/hns3: delete unused macro Min Hu (Connor)
2021-04-20 8:59 ` [dpdk-dev] [PATCH 2/5] net/hns3: fix enum variable used as boolean Min Hu (Connor)
2021-04-20 8:59 ` [dpdk-dev] [PATCH 3/5] net/hns3: fix unchecked function call Min Hu (Connor)
2021-04-20 8:59 ` [dpdk-dev] [PATCH 4/5] doc: update hns3 feature list Min Hu (Connor)
2021-04-20 10:34 ` Ferruh Yigit
2021-04-20 8:59 ` Min Hu (Connor) [this message]
2021-04-20 10:56 ` [dpdk-dev] [PATCH 0/5] fixes for hns3 PMD Ferruh Yigit
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=1618909192-17431-6-git-send-email-humin29@huawei.com \
--to=humin29@huawei.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.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).