DPDK patches and discussions
 help / color / mirror / Atom feed
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 18.02 rc2
Date: Mon, 29 Jan 2018 19:30:04 +0000	[thread overview]
Message-ID: <20180129193004.36797-1-pablo.de.lara.guarch@intel.com> (raw)

The following changes since commit 1dd133ae073d9e2bcf6f471f3b831385aa0051c4:

  service: restrict finalize to internal usage (2018-01-29 19:24:45 +0100)

are available in the Git repository at:

  http://dpdk.org/git/next/dpdk-next-crypto 

for you to fetch changes up to 8bf542fda490ed5059d8149e5c757c3e6e9af830:

  crypto/qat: fix truncated response ring value (2018-01-29 19:22:33 +0000)

----------------------------------------------------------------
Akhil Goyal (3):
      doc: update feature list for cryptodevs
      crypto/dpaa2_sec: support scatter gather
      crypto/dpaa_sec: support scatter gather

Fan Zhang (2):
      examples/ipsec_secgw: fix security session
      app/test-crypto-perf: fix out-of-bounds array access

Fiona Trahe (3):
      crypto/qat: fix null auth algo issue
      test/crypto: improve NULL authentication validation
      crypto/qat: fix truncated response ring value

Tomasz Jozwiak (3):
      crypto/qat: fix out-of-bounds compiler error
      crypto/qat: fix typo in error message
      crypto/qat: fix parameter type

Zhiyong Yang (1):
      lib: fix wrong cast

 app/test-crypto-perf/main.c                        |  10 +-
 doc/guides/cryptodevs/features/aesni_gcm.ini       |   1 +
 doc/guides/cryptodevs/features/default.ini         |   1 +
 doc/guides/cryptodevs/features/dpaa2_sec.ini       |   1 +
 doc/guides/cryptodevs/features/dpaa_sec.ini        |   1 +
 doc/guides/cryptodevs/features/null.ini            |   1 +
 doc/guides/cryptodevs/features/openssl.ini         |   1 +
 doc/guides/cryptodevs/features/qat.ini             |   1 +
 drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c        | 588 +++++++++++++++++++--
 drivers/crypto/dpaa_sec/dpaa_sec.c                 | 501 +++++++++++++++++-
 .../qat/qat_adf/adf_transport_access_macros.h      |   1 +
 drivers/crypto/qat/qat_crypto.c                    |  36 +-
 examples/ipsec-secgw/ipsec-secgw.c                 |  10 +-
 lib/librte_cryptodev/rte_cryptodev.c               |   2 +-
 lib/librte_security/rte_security.c                 |   2 +-
 test/test/test_cryptodev.c                         |  82 ++-
 test/test/test_cryptodev_aes_test_vectors.h        |  27 +-
 test/test/test_cryptodev_hash_test_vectors.h       |  16 +
 18 files changed, 1188 insertions(+), 94 deletions(-)

             reply	other threads:[~2018-01-29 19:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-29 19:30 Pablo de Lara [this message]
2018-01-29 23:18 ` 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=20180129193004.36797-1-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).