DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <akhil.goyal@nxp.com>
To: thomas@monjalon.net
Cc: dev@dpdk.org
Subject: [dpdk-dev] [pull-request] next-crypto 19.11 rc4
Date: Mon, 25 Nov 2019 18:00:15 +0530	[thread overview]
Message-ID: <20191125123015.2259-1-akhil.goyal@nxp.com> (raw)

The following changes since commit c143928d8977f9d118078a0e6545d9058bbdbe52:

  devtools: disable automatic probing in null testing (2019-11-24 23:52:02 +0100)

are available in the Git repository at:

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

for you to fetch changes up to cece4cc134c5b1d73bd9bc62ea3c528ad93ce6c9:

  crypto/ccp: fix capabilities for digest size (2019-11-25 15:31:36 +0530)

----------------------------------------------------------------
Amaranath Somalapuram (5):
      doc: fix app usage in CCP guide
      crypto/ccp: fix max qp and burst size
      crypto/ccp: fix CPU authentication crash
      crypto/ccp: fix scheduling of pkt burst
      crypto/ccp: fix capabilities for digest size

Archana Muniganti (1):
      app/crypto-perf: fix incorrect input data for AEAD decrypt

 app/test-crypto-perf/cperf_test_verify.c | 14 ++++++--
 doc/guides/cryptodevs/ccp.rst            | 32 +++++++++---------
 drivers/crypto/ccp/ccp_crypto.c          | 24 +++++++++-----
 drivers/crypto/ccp/ccp_crypto.h          |  7 ++--
 drivers/crypto/ccp/ccp_dev.h             |  2 +-
 drivers/crypto/ccp/ccp_pmd_ops.c         | 28 ++++++++--------
 drivers/crypto/ccp/ccp_pmd_private.h     |  6 ++--
 drivers/crypto/ccp/rte_ccp_pmd.c         | 57 ++++++++++++++++++++++----------
 8 files changed, 107 insertions(+), 63 deletions(-)

             reply	other threads:[~2019-11-25 12:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-25 12:30 Akhil Goyal [this message]
2019-11-26 14:34 ` 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=20191125123015.2259-1-akhil.goyal@nxp.com \
    --to=akhil.goyal@nxp.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).