From: "Mcnamara, John" <john.mcnamara@intel.com>
To: Boris Pismenny <borisp@mellanox.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "akhil.goyal@nxp.com" <akhil.goyal@nxp.com>,
"Doherty, Declan" <declan.doherty@intel.com>,
"De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
"hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>,
"Nicolau, Radu" <radu.nicolau@intel.com>,
"aviadye@mellanox.com" <aviadye@mellanox.com>,
"thomas@monjalon.net" <thomas@monjalon.net>,
"sandeep.malik@nxp.com" <sandeep.malik@nxp.com>,
"jerin.jacob@caviumnetworks.com" <jerin.jacob@caviumnetworks.com>,
"nelio.laranjeiro@6wind.com" <nelio.laranjeiro@6wind.com>,
"liranl@mellanox.com" <liranl@mellanox.com>
Subject: Re: [dpdk-dev] [PATCH 1/2] doc: add details of rte_flow security actions
Date: Mon, 18 Sep 2017 11:14:29 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE23EDA926D@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <1505649991-3463-2-git-send-email-borisp@mellanox.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Boris Pismenny
> Sent: Sunday, September 17, 2017 1:07 PM
> To: dev@dpdk.org
> Cc: akhil.goyal@nxp.com; Doherty, Declan <declan.doherty@intel.com>; De
> Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>;
> hemant.agrawal@nxp.com; Nicolau, Radu <radu.nicolau@intel.com>;
> borisp@mellanox.com; aviadye@mellanox.com; thomas@monjalon.net;
> sandeep.malik@nxp.com; jerin.jacob@caviumnetworks.com;
> nelio.laranjeiro@6wind.com; liranl@mellanox.com
> Subject: [dpdk-dev] [PATCH 1/2] doc: add details of rte_flow security
> actions
>
> Signed-off-by: Boris Pismenny <borisp@mellanox.com>
Thanks for the docs. Minor comments below.
> +
> +Multiple flows can be configured to use the same security session.
> +
> +- Non-terminating by default.
This is a single bullet point list and it seems disconnected from the previous
line. Maybe convert it to a sentence instead.
> +
> +.. _table_rte_flow_action_security
This is missing a colon at the end and causes a doc build warning.
> +Usage example, configure IPsec inline using INLINE_CRYPTO security
> session:
This doesn't seem to connect to the following paragraph. Maybe something
like:
The following is an example of configuring IPsec inline using the
INLINE_CRYPTO security session:
Reviewed-by: John McNamara <john.mcnamara@intel.com>
next prev parent reply other threads:[~2017-09-18 11:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-17 12:06 [dpdk-dev] [PATCH 0/2] Document rte_flow security action Boris Pismenny
2017-09-17 12:06 ` [dpdk-dev] [PATCH 1/2] doc: add details of rte_flow security actions Boris Pismenny
2017-09-18 11:14 ` Mcnamara, John [this message]
2017-09-17 12:06 ` [dpdk-dev] [PATCH 2/2] ethdev: update documentation for security action Boris Pismenny
2017-09-18 11:18 ` Mcnamara, John
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=B27915DBBA3421428155699D51E4CFE23EDA926D@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=aviadye@mellanox.com \
--cc=borisp@mellanox.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=jerin.jacob@caviumnetworks.com \
--cc=liranl@mellanox.com \
--cc=nelio.laranjeiro@6wind.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=radu.nicolau@intel.com \
--cc=sandeep.malik@nxp.com \
--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).