From: Akhil Goyal <akhil.goyal@nxp.com>
To: Tomasz Cel <tomaszx.cel@intel.com>, dev@dpdk.org
Cc: stable@dpdk.org, marko.kovacevic@intel.com
Subject: Re: [dpdk-dev] [PATCH v2] doc/crypto: fix missing CCM to QAT feature list
Date: Wed, 26 Sep 2018 17:56:24 +0530 [thread overview]
Message-ID: <bb2ede79-5405-367d-8e59-90a12329b9f9@nxp.com> (raw)
In-Reply-To: <1537338438-2335-1-git-send-email-tomaszx.cel@intel.com>
On 9/19/2018 11:57 AM, Tomasz Cel wrote:
> 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(+)
>
Applied to dpdk-next-crypto
cc: stable@dpdk.org
Thanks
prev parent reply other threads:[~2018-09-26 12:26 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 ` [dpdk-dev] [PATCH v2] doc/crypto: fix missing CCM to " Tomasz Cel
2018-09-19 7:28 ` Trahe, Fiona
2018-09-19 8:09 ` Kovacevic, Marko
2018-09-26 12:26 ` Akhil Goyal [this message]
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=bb2ede79-5405-367d-8e59-90a12329b9f9@nxp.com \
--to=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=marko.kovacevic@intel.com \
--cc=stable@dpdk.org \
--cc=tomaszx.cel@intel.com \
/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).