From: "Zhang, Yuying" <yuying.zhang@intel.com>
To: Michael Baum <michaelba@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Matan Azrad <matan@nvidia.com>,
Thomas Monjalon <thomas@monjalon.net>,
Raslan Darawsheh <rasland@nvidia.com>,
"Singh, Aman Deep" <aman.deep.singh@intel.com>,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
"jackmin@mellanox.com" <jackmin@mellanox.com>,
"dongz@mellanox.com" <dongz@mellanox.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [PATCH 1/6] doc: fix underlines too long in testpmd documentation
Date: Fri, 11 Nov 2022 07:07:57 +0000 [thread overview]
Message-ID: <DM6PR11MB351648F4F2B74956870615B38E009@DM6PR11MB3516.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20221110141506.335016-2-michaelba@nvidia.com>
> -----Original Message-----
> From: Michael Baum <michaelba@nvidia.com>
> Sent: 2022年11月10日 22:15
> To: dev@dpdk.org
> Cc: Matan Azrad <matan@nvidia.com>; Thomas Monjalon
> <thomas@monjalon.net>; Raslan Darawsheh <rasland@nvidia.com>; Singh,
> Aman Deep <aman.deep.singh@intel.com>; Zhang, Yuying
> <yuying.zhang@intel.com>; Andrew Rybchenko
> <andrew.rybchenko@oktetlabs.ru>; jackmin@mellanox.com;
> dongz@mellanox.com; stable@dpdk.org
> Subject: [PATCH 1/6] doc: fix underlines too long in testpmd documentation
>
> 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: jackmin@mellanox.com
> Cc: dongz@mellanox.com
> Cc: stable@dpdk.org
>
> Signed-off-by: Michael Baum <michaelba@nvidia.com>
Acked-by: Yuying Zhang <Yuying.Zhang@intel.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
next prev parent reply other threads:[~2022-11-11 7:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221110141506.335016-1-michaelba@nvidia.com>
2022-11-10 14:15 ` Michael Baum
2022-11-11 7:07 ` Zhang, Yuying [this message]
2022-11-10 14:15 ` [PATCH 2/6] doc: fix the colon type in listing aged flow rules Michael Baum
2022-11-10 14:15 ` [PATCH 3/6] doc: fix miss blank line in testpmd flow syntax doc Michael Baum
2022-11-11 7:02 ` Zhang, Yuying
[not found] ` <20221116125628.1026877-1-michaelba@nvidia.com>
2022-11-16 12:56 ` [PATCH v2 1/6] doc: fix underlines too long in testpmd documentation Michael Baum
2022-11-16 12:56 ` [PATCH v2 2/6] doc: fix the colon type in listing aged flow rules Michael Baum
2022-11-16 12:56 ` [PATCH v2 3/6] doc: fix miss blank line in testpmd flow syntax doc Michael Baum
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=DM6PR11MB351648F4F2B74956870615B38E009@DM6PR11MB3516.namprd11.prod.outlook.com \
--to=yuying.zhang@intel.com \
--cc=aman.deep.singh@intel.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=dongz@mellanox.com \
--cc=jackmin@mellanox.com \
--cc=matan@nvidia.com \
--cc=michaelba@nvidia.com \
--cc=rasland@nvidia.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
/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).