From: Pablo de Lara <pablo.de.lara.guarch@intel.com>
To: thomas@monjalon.net
Cc: dev@dpdk.org
Subject: [dpdk-dev] [pull-request] next-crypto 17.05 RC3
Date: Fri, 28 Apr 2017 16:51:16 +0100 [thread overview]
Message-ID: <1493394676-153283-1-git-send-email-pablo.de.lara.guarch@intel.com> (raw)
The following changes since commit f051679dc577d93d177e6eddefaba28a69d9955f:
devtools: list stable commits without fixline (2017-04-28 12:05:03 +0200)
are available in the git repository at:
http://dpdk.org/git/next/dpdk-next-crypto
for you to fetch changes up to d295885b29b8aa4bf11e54bd31f4ee456266fd44:
cryptodev: fix API digest length comments (2017-04-28 16:46:19 +0100)
----------------------------------------------------------------
Arek Kusztal (4):
crypto/openssl: fix AAD capabilities for AES-GCM
crypto/qat: fix AAD capabilities for AES-GCM
cryptodev: fix API AAD comments
doc: add limitation of AAD size for QAT
Fiona Trahe (1):
cryptodev: fix API digest length comments
Gage Eads (1):
crypto/qat: fix dequeue count stats retrieval
Pablo de Lara (2):
crypto/openssl: fix AES GCM capability
examples/l2fwd-crypto: fix wrong array index
doc/guides/cryptodevs/qat.rst | 1 +
drivers/crypto/openssl/rte_openssl_pmd_ops.c | 10 +++++-----
drivers/crypto/qat/qat_crypto.c | 4 ++--
drivers/crypto/qat/qat_crypto_capabilities.h | 6 +++---
examples/l2fwd-crypto/main.c | 2 +-
lib/librte_cryptodev/rte_crypto_sym.h | 22 +++++++++++++---------
6 files changed, 25 insertions(+), 20 deletions(-)
next reply other threads:[~2017-04-28 15:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-28 15:51 Pablo de Lara [this message]
2017-05-01 12:39 ` Thomas Monjalon
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=1493394676-153283-1-git-send-email-pablo.de.lara.guarch@intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=dev@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).