From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Thomas Monjalon <thomas@monjalon.net>, Ori Kam <orika@nvidia.com>,
Jie Wang <jie1x.wang@intel.com>,
Ferruh Yigit <ferruh.yigit@intel.com>,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Wenjun Wu <wenjun1.wu@intel.com>
Cc: David Marchand <david.marchand@redhat.com>, <dev@dpdk.org>,
<stable@dpdk.org>
Subject: [PATCH v4 7/8] doc: fix description of L2TPV2 flow item
Date: Thu, 26 Jan 2023 13:17:58 +0000 [thread overview]
Message-ID: <20230126131759.3887632-8-ferruh.yigit@amd.com> (raw)
In-Reply-To: <20230126131759.3887632-1-ferruh.yigit@amd.com>
From: Thomas Monjalon <thomas@monjalon.net>
The flow item structure includes the protocol definition
from the directory lib/net/, so it is reflected in the guide.
Section title underlining is also fixed around.
Fixes: 3a929df1f286 ("ethdev: support L2TPv2 and PPP procotol")
Cc: stable@dpdk.org
Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
---
Cc: jie1x.wang@intel.com
---
doc/guides/prog_guide/rte_flow.rst | 13 +++----------
1 file changed, 3 insertions(+), 10 deletions(-)
diff --git a/doc/guides/prog_guide/rte_flow.rst b/doc/guides/prog_guide/rte_flow.rst
index 8bf85df2f611..c01b53aad8ed 100644
--- a/doc/guides/prog_guide/rte_flow.rst
+++ b/doc/guides/prog_guide/rte_flow.rst
@@ -1485,22 +1485,15 @@ rte_flow_flex_item_create() routine.
value and mask.
Item: ``L2TPV2``
-^^^^^^^^^^^^^^^^^^^
+^^^^^^^^^^^^^^^^
Matches a L2TPv2 header.
-- ``flags_version``: flags(12b), version(4b).
-- ``length``: total length of the message.
-- ``tunnel_id``: identifier for the control connection.
-- ``session_id``: identifier for a session within a tunnel.
-- ``ns``: sequence number for this date or control message.
-- ``nr``: sequence number expected in the next control message to be received.
-- ``offset_size``: offset of payload data.
-- ``offset_padding``: offset padding, variable length.
+- ``hdr``: header definition (``rte_l2tpv2.h``).
- Default ``mask`` matches flags_version only.
Item: ``PPP``
-^^^^^^^^^^^^^^^^^^^
+^^^^^^^^^^^^^
Matches a PPP header.
--
2.25.1
next prev parent reply other threads:[~2023-01-26 13:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221025214410.715864-1-thomas@monjalon.net>
[not found] ` <20230120171902.4188088-1-ferruh.yigit@amd.com>
2023-01-20 17:19 ` [PATCH v2 " Ferruh Yigit
[not found] ` <20230124090300.247915-1-ferruh.yigit@amd.com>
2023-01-24 9:02 ` [PATCH v3 " Ferruh Yigit
[not found] ` <20230126131759.3887632-1-ferruh.yigit@amd.com>
2023-01-26 13:17 ` Ferruh Yigit [this message]
[not found] ` <20230126161904.864517-1-ferruh.yigit@amd.com>
2023-01-26 16:19 ` [PATCH v5 " Ferruh Yigit
2023-02-02 9:56 ` Andrew Rybchenko
[not found] ` <20230202124500.2578857-1-ferruh.yigit@amd.com>
2023-02-02 12:44 ` [PATCH v6 " Ferruh Yigit
[not found] ` <20230203164854.602595-1-ferruh.yigit@amd.com>
2023-02-03 16:48 ` [PATCH v7 6/7] " 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=20230126131759.3887632-8-ferruh.yigit@amd.com \
--to=ferruh.yigit@amd.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jie1x.wang@intel.com \
--cc=orika@nvidia.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--cc=wenjun1.wu@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).