The literal text of the commands to use were not displayed properly because of
a double ":" at the end of the preceding text, meaning that the ".. code-block"
marker got recognised as the literal text to include. Change the double colon
to single, and also indent the line continuation in the multi-line flow-create
command.
Fixes: 03f976012304 ("net/cpfl: adapt FXP to flow engine")
Cc: [email protected]
Signed-off-by: Bruce Richardson <[email protected]>
---
doc/guides/nics/cpfl.rst | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/doc/guides/nics/cpfl.rst b/doc/guides/nics/cpfl.rst index
54a3015aa0..bc42c524ea 100644
--- a/doc/guides/nics/cpfl.rst
+++ b/doc/guides/nics/cpfl.rst
@@ -218,14 +218,14 @@ low level hardware resources.
dpdk-testpmd -l 0,1 -a
0000:af:00.6,vport=[0-1],flow_parser="refpkg.json" -- -i
#. Create one flow to forward ETH-IPV4-TCP from I/O port to a local(CPF's)
vport. Flow should be created on
- vport X. Group M should match fxp module. Action port_representor Y means
forward packet to local vport Y::
+ vport X. Group M should match fxp module. Action port_representor Y means
forward packet to local vport Y:
.. code-block:: console
flow create X ingress group M pattern eth dst is 00:01:00:00:03:14 /
ipv4 src is 192.168.0.1 \
- dst is 192.168.0.2 / tcp / end actions port_representor port_id Y / end
+ dst is 192.168.0.2 / tcp / end actions port_representor
+ port_id Y / end
-#. Send a matched packet, and it should be displayed on PMD::
+#. Send a matched packet, and it should be displayed on PMD:
.. code-block:: console
Looks good to me - thanks Bruce!
Acked-by: Praveen Shetty <[email protected]>
--
2.48.1
