DPDK patches and discussions
 help / color / mirror / Atom feed
From: Tomasz Cel <tomaszx.cel@intel.com>
To: dev@dpdk.org
Cc: stable@dpdk.org, akhil.goyal@nxp.com, marko.kovacevic@intel.com,
	Tomasz Cel <tomaszx.cel@intel.com>
Subject: [dpdk-dev] [PATCH v2] doc/crypto: fix missing CCM to QAT feature list
Date: Wed, 19 Sep 2018 08:27:18 +0200	[thread overview]
Message-ID: <1537338438-2335-1-git-send-email-tomaszx.cel@intel.com> (raw)
In-Reply-To: <1536686639-19057-1-git-send-email-tomaszx.cel@intel.com>

Update the QAT documentation to show that it supports CCM.

Fixes: ab56c4d9ed9a ("crypto/qat: support AES-CCM")

Signed-off-by: Tomasz Cel <tomaszx.cel@intel.com>
---
 doc/guides/cryptodevs/features/qat.ini | 3 +++
 doc/guides/cryptodevs/qat.rst          | 1 +
 2 files changed, 4 insertions(+)

diff --git a/doc/guides/cryptodevs/features/qat.ini b/doc/guides/cryptodevs/features/qat.ini
index 29d865e..220291b 100644
--- a/doc/guides/cryptodevs/features/qat.ini
+++ b/doc/guides/cryptodevs/features/qat.ini
@@ -56,3 +56,6 @@ ZUC EIA3     = Y
 AES GCM (128) = Y
 AES GCM (192) = Y
 AES GCM (256) = Y
+AES CCM (128) = Y
+AES CCM (192) = Y
+AES CCM (256) = Y
diff --git a/doc/guides/cryptodevs/qat.rst b/doc/guides/cryptodevs/qat.rst
index af10799..b09624f 100644
--- a/doc/guides/cryptodevs/qat.rst
+++ b/doc/guides/cryptodevs/qat.rst
@@ -66,6 +66,7 @@ Hash algorithms:
 Supported AEAD algorithms:
 
 * ``RTE_CRYPTO_AEAD_AES_GCM``
+* ``RTE_CRYPTO_AEAD_AES_CCM``
 
 
 Limitations
-- 
2.7.4

  parent reply	other threads:[~2018-09-19  6:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-11 17:23 [dpdk-dev] [PATCH] doc/fix: add CCM to the " Tomasz Cel
2018-09-13 13:41 ` Kovacevic, Marko
2018-09-19  6:27 ` Tomasz Cel [this message]
2018-09-19  7:28   ` [dpdk-dev] [PATCH v2] doc/crypto: fix missing CCM to " Trahe, Fiona
2018-09-19  8:09   ` Kovacevic, Marko
2018-09-26 12:26   ` Akhil Goyal

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=1537338438-2335-1-git-send-email-tomaszx.cel@intel.com \
    --to=tomaszx.cel@intel.com \
    --cc=akhil.goyal@nxp.com \
    --cc=dev@dpdk.org \
    --cc=marko.kovacevic@intel.com \
    --cc=stable@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).