From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "Trahe, Fiona" <fiona.trahe@intel.com>,
"Doherty, Declan" <declan.doherty@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2 0/5] L2fwd-crypto fixes
Date: Fri, 20 Jul 2018 10:41:12 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8977F8FE014@IRSMSX107.ger.corp.intel.com> (raw)
In-Reply-To: <348A99DA5F5B7549AA880327E580B435895DDE19@IRSMSX101.ger.corp.intel.com>
Hi Fiona,
> -----Original Message-----
> From: Trahe, Fiona
> Sent: Friday, July 20, 2018 10:02 AM
> To: De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>; Doherty, Declan
> <declan.doherty@intel.com>
> Cc: dev@dpdk.org; Trahe, Fiona <fiona.trahe@intel.com>
> Subject: RE: [PATCH v2 0/5] L2fwd-crypto fixes
>
> Hi Pablo,
>
> > -----Original Message-----
> > From: De Lara Guarch, Pablo
> > Sent: Thursday, July 19, 2018 9:40 AM
> > To: Doherty, Declan <declan.doherty@intel.com>; Trahe, Fiona
> <fiona.trahe@intel.com>
> > Cc: dev@dpdk.org; De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>
> > Subject: [PATCH v2 0/5] L2fwd-crypto fixes
> >
> > v2 changes:
> > - Split patch into multiple patches for better review
> > - First two patches are fixes for previous releases
> >
> > Pablo de Lara (5):
> > examples/l2fwd-crypto: check return value on IV size check
> > examples/l2fwd-crypto: skip device not supporting operation
> > examples/l2fwd-crypto: separate IV check from xform setting
> > examples/l2fwd-crypto: fix session mempool size
> > examples/l2fwd-crypto: remove duplicated capability check
> >
> > examples/l2fwd-crypto/main.c | 539 +++++++++++++++++++++++++++---------
> -------
> > 1 file changed, 340 insertions(+), 199 deletions(-)
> >
> > --
> > 2.14.4
> One minor comment in patch 4, apart from that
> Series-acked-by: Fiona Trahe <fiona.trahe@intel.com>
Thanks for the review. I will make that change on the fly when applying the patchset,
as it is a minor change, to avoid spam.
next prev parent reply other threads:[~2018-07-20 10:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-17 10:38 [dpdk-dev] [PATCH] examples/l2fwd-crypto: fix session mempool size Pablo de Lara
2018-07-19 8:39 ` [dpdk-dev] [PATCH v2 0/5] L2fwd-crypto fixes Pablo de Lara
2018-07-19 8:39 ` [dpdk-dev] [PATCH v2 1/5] examples/l2fwd-crypto: check return value on IV size check Pablo de Lara
2018-07-19 8:39 ` [dpdk-dev] [PATCH v2 2/5] examples/l2fwd-crypto: skip device not supporting operation Pablo de Lara
2018-07-19 8:39 ` [dpdk-dev] [PATCH v2 3/5] examples/l2fwd-crypto: separate IV check from xform setting Pablo de Lara
2018-07-19 8:39 ` [dpdk-dev] [PATCH v2 4/5] examples/l2fwd-crypto: fix session mempool size Pablo de Lara
2018-07-20 8:53 ` Trahe, Fiona
2018-07-19 8:39 ` [dpdk-dev] [PATCH v2 5/5] examples/l2fwd-crypto: remove duplicated capability check Pablo de Lara
2018-07-20 9:01 ` [dpdk-dev] [PATCH v2 0/5] L2fwd-crypto fixes Trahe, Fiona
2018-07-20 10:41 ` De Lara Guarch, Pablo [this message]
2018-07-20 10:45 ` De Lara Guarch, Pablo
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=E115CCD9D858EF4F90C690B0DCB4D8977F8FE014@IRSMSX107.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
/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).