In testpmd documentation, there are two underlines which should not match the length of the text above.
This patch update them to be align with the guideline [1]. [1] https://doc.dpdk.org/guides/contributing/documentation.html#section-headers Fixes: a69c335d56b5 ("doc: add flow dump command in testpmd guide") Fixes: 0e459ffa0889 ("app/testpmd: support flow aging") Cc: jack...@mellanox.com Cc: do...@mellanox.com Cc: sta...@dpdk.org Signed-off-by: Michael Baum <michae...@nvidia.com> --- doc/guides/testpmd_app_ug/testpmd_funcs.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/guides/testpmd_app_ug/testpmd_funcs.rst b/doc/guides/testpmd_app_ug/testpmd_funcs.rst index 96c5ae0fe4..b5649d9d9a 100644 --- a/doc/guides/testpmd_app_ug/testpmd_funcs.rst +++ b/doc/guides/testpmd_app_ug/testpmd_funcs.rst @@ -4240,7 +4240,7 @@ Disabling isolated mode:: testpmd> Dumping HW internal information -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ``flow dump`` dumps the hardware's internal representation information of all flows. It is bound to ``rte_flow_dev_dump()``:: @@ -4256,7 +4256,7 @@ Otherwise, it will complain error occurred:: Caught error type [...] ([...]): [...] Listing and destroying aged flow rules -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ``flow aged`` simply lists aged flow rules be get from api ``rte_flow_get_aged_flows``, and ``destroy`` parameter can be used to destroy those flow rules in PMD. -- 2.25.1
