From: Pablo de Lara <pablo.de.lara.guarch@intel.com>
To: declan.doherty@intel.com
Cc: dev@dpdk.org, Pablo de Lara <pablo.de.lara.guarch@intel.com>
Subject: [dpdk-dev] [PATCH 0/3] L2fwd-crypto fixes
Date: Tue, 18 Jul 2017 08:58:15 +0100 [thread overview]
Message-ID: <20170718075818.75643-1-pablo.de.lara.guarch@intel.com> (raw)
After the changes added to include AEAD algorithm
specific parameters, there were some parameters
that were being set wrong or not even set.
Pablo de Lara (3):
examples/l2fwd-crypto: fix digest length
examples/l2fwd-crypto: fix AEAD IV setting
examples/l2fwd-crypto: fix AEAD key setting
examples/l2fwd-crypto/main.c | 11 +++++++++--
1 file changed, 9 insertions(+), 2 deletions(-)
--
2.9.4
next reply other threads:[~2017-07-18 15:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-18 7:58 Pablo de Lara [this message]
2017-07-18 7:58 ` [dpdk-dev] [PATCH 1/3] examples/l2fwd-crypto: fix digest length Pablo de Lara
2017-07-18 7:58 ` [dpdk-dev] [PATCH 2/3] examples/l2fwd-crypto: fix AEAD IV setting Pablo de Lara
2017-07-18 7:58 ` [dpdk-dev] [PATCH 3/3] examples/l2fwd-crypto: fix AEAD key setting Pablo de Lara
2017-07-19 8:05 ` [dpdk-dev] [PATCH 0/3] L2fwd-crypto fixes 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=20170718075818.75643-1-pablo.de.lara.guarch@intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=declan.doherty@intel.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).