DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <gakhil@marvell.com>
To: <thomas@monjalon.net>
Cc: <dev@dpdk.org>
Subject: [pull-request] next-crypto 21.11 rc4
Date: Wed, 24 Nov 2021 14:05:03 +0530	[thread overview]
Message-ID: <20211124083503.3613236-1-gakhil@marvell.com> (raw)

The following changes since commit 0c6e27549c03695f85d949f5195a166b449b419c:

  version: 21.11-rc3 (2021-11-17 20:19:47 +0100)

are available in the Git repository at:

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

for you to fetch changes up to 7cdcc0f5c875bc95b72d66054b632825c3e16e4f:

  app/test-crypto-perf: fix segment size for IPsec (2021-11-24 01:18:04 +0530)

----------------------------------------------------------------
Gagandeep Singh (3):
      drivers/crypto: fix IPsec TTL decrement option
      drivers/crypto: return ENOTSUP for SA lifetime
      app/test-crypto-perf: fix segment size for IPsec

Pablo de Lara (2):
      crypto/ipsec_mb: fix cipher key setting
      doc: support IPsec Multi-buffer lib v1.1

Raja Zidane (1):
      crypto/mlx5: fix max number of QPs capability

 app/test-crypto-perf/cperf_options_parsing.c | 10 +++++++++-
 doc/guides/cryptodevs/aesni_gcm.rst          |  8 ++++----
 doc/guides/cryptodevs/aesni_mb.rst           |  8 ++++----
 doc/guides/cryptodevs/kasumi.rst             |  8 ++++----
 doc/guides/cryptodevs/snow3g.rst             |  8 ++++----
 doc/guides/cryptodevs/zuc.rst                |  8 ++++----
 drivers/crypto/caam_jr/caam_jr.c             | 11 +++++++++--
 drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c  |  9 ++++++++-
 drivers/crypto/dpaa_sec/dpaa_sec.c           | 10 +++++++++-
 drivers/crypto/ipsec_mb/pmd_aesni_mb.c       | 15 ++++++++-------
 drivers/crypto/mlx5/mlx5_crypto.c            |  2 +-
 11 files changed, 64 insertions(+), 33 deletions(-)

             reply	other threads:[~2021-11-24  8:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-24  8:35 Akhil Goyal [this message]
2021-11-24 11:48 ` 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=20211124083503.3613236-1-gakhil@marvell.com \
    --to=gakhil@marvell.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).