From: Jack Min <jackmin@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] [PATCH 0/2] doc update for rte flow shared action
Date: Tue, 2 Feb 2021 12:23:48 +0000 [thread overview]
Message-ID: <cover.1612266977.git.jackmin@nvidia.com> (raw)
This series update documents as following:
1. Add more information about shared action in rte_flow.rst.
2. Group all supported shared actions in mlx5.rst
Xiaoyu Min (2):
doc: more info of rte flow shared action
doc: group mlx5 shared actions
doc/guides/nics/mlx5.rst | 30 +++++++++++++++++++++---------
doc/guides/prog_guide/rte_flow.rst | 7 +++++++
2 files changed, 28 insertions(+), 9 deletions(-)
--
2.30.0
next reply other threads:[~2021-02-02 12:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-02 12:23 Jack Min [this message]
2021-02-02 12:23 ` [dpdk-dev] [PATCH 1/2] doc: more info of " Jack Min
2021-02-03 7:50 ` Ori Kam
2021-02-03 9:02 ` Asaf Penso
2021-02-03 11:58 ` Ferruh Yigit
2021-02-02 12:23 ` [dpdk-dev] [PATCH 2/2] doc: group mlx5 shared actions Jack Min
2021-02-03 9:02 ` Asaf Penso
2021-02-03 11:59 ` [dpdk-dev] [PATCH 0/2] doc update for rte flow shared action 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=cover.1612266977.git.jackmin@nvidia.com \
--to=jackmin@nvidia.com \
--cc=dev@dpdk.org \
/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).