From: Rami Rosen <ramirose@gmail.com>
To: dev@dpdk.org
Cc: xuemingl@mellanox.com, Rami Rosen <ramirose@gmail.com>
Subject: [dpdk-dev] [PATCH] doc: fix wrong tag for Inner RSS
Date: Fri, 1 Mar 2019 13:10:10 +0200 [thread overview]
Message-ID: <20190301111010.21990-1-ramirose@gmail.com> (raw)
This patch fixes a wrong tag in guides/nics/features.rst.
The features tags should be, according to the
"Features Overview" section in this doc, one of the following:
"uses", "implements", "provides", or "related".
Hence in Inner RSS section, it should be "uses"
instead of "users".
Fixes: d0a87d9aa8de ("doc: update mlx5 guide on tunnel offloading")
Signed-off-by: Rami Rosen <ramirose@gmail.com>
---
doc/guides/nics/features.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/guides/nics/features.rst b/doc/guides/nics/features.rst
index d3f904839..c5bf32222 100644
--- a/doc/guides/nics/features.rst
+++ b/doc/guides/nics/features.rst
@@ -285,7 +285,7 @@ Inner RSS
Supports RX RSS hashing on Inner headers.
-* **[users] rte_flow_action_rss**: ``level``.
+* **[uses] rte_flow_action_rss**: ``level``.
* **[provides] mbuf**: ``mbuf.ol_flags:PKT_RX_RSS_HASH``, ``mbuf.rss``.
--
2.19.2
next reply other threads:[~2019-03-01 11:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-01 11:10 Rami Rosen [this message]
2019-03-04 18:11 ` 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=20190301111010.21990-1-ramirose@gmail.com \
--to=ramirose@gmail.com \
--cc=dev@dpdk.org \
--cc=xuemingl@mellanox.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).