From: "Trahe, Fiona" <fiona.trahe@intel.com>
To: "Cel, TomaszX" <tomaszx.cel@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
"akhil.goyal@nxp.com" <akhil.goyal@nxp.com>,
"Kovacevic, Marko" <marko.kovacevic@intel.com>,
"Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>,
"mattias.ronnblom@ericsson.com" <mattias.ronnblom@ericsson.com>,
"Trahe, Fiona" <fiona.trahe@intel.com>
Subject: Re: [dpdk-dev] [PATCH v3 3/3] doc/qat: update AES-CMAC documentation
Date: Tue, 9 Oct 2018 14:37:57 +0000 [thread overview]
Message-ID: <348A99DA5F5B7549AA880327E580B43589646B6A@IRSMSX101.ger.corp.intel.com> (raw)
In-Reply-To: <1539019005-13210-4-git-send-email-tomaszx.cel@intel.com>
> -----Original Message-----
> From: Cel, TomaszX
> Sent: Monday, October 8, 2018 6:17 PM
> To: dev@dpdk.org
> Cc: stable@dpdk.org; Trahe, Fiona <fiona.trahe@intel.com>; akhil.goyal@nxp.com; Kovacevic, Marko
> <marko.kovacevic@intel.com>; Kusztal, ArkadiuszX <arkadiuszx.kusztal@intel.com>;
> mattias.ronnblom@ericsson.com; Cel, TomaszX <tomaszx.cel@intel.com>
> Subject: [PATCH v3 3/3] doc/qat: update AES-CMAC documentation
>
> Update the QAT documentation to show that it supports AES-CMAC.
>
> Signed-off-by: Tomasz Cel <tomaszx.cel@intel.com>
Nack.
The capabilities change should be in the PMD patch 1/3
We'll send a v4 shortly.
next prev parent reply other threads:[~2018-10-09 14:38 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-28 18:10 [dpdk-dev] [PATCH 0/3] add AES-CMAC support Tomasz Cel
2018-09-28 18:10 ` [dpdk-dev] [PATCH 1/3] crypto/qat: add support AES-CMAC Tomasz Cel
2018-09-28 18:10 ` [dpdk-dev] [PATCH 2/3] test/qat: test for AES-CMAC Tomasz Cel
2018-09-28 18:10 ` [dpdk-dev] [PATCH 3/3] doc/qat: add AES-CMAC to the QAT feature list Tomasz Cel
2018-10-04 11:22 ` [dpdk-dev] [PATCH v2 0/3] add AES-CMAC support Tomasz Cel
2018-10-04 11:22 ` [dpdk-dev] [PATCH v2 1/3] crypto/qat: add support AES-CMAC Tomasz Cel
2018-10-05 12:02 ` Mattias Rönnblom
2018-10-05 13:27 ` Trahe, Fiona
2018-10-04 11:22 ` [dpdk-dev] [PATCH v2 2/3] test/qat: test for AES-CMAC Tomasz Cel
2018-10-04 11:22 ` [dpdk-dev] [PATCH v2 3/3] doc/qat: add AES-CMAC to the QAT feature list Tomasz Cel
2018-10-04 11:47 ` [dpdk-dev] [PATCH v2 0/3] add AES-CMAC support Trahe, Fiona
2018-10-08 17:16 ` [dpdk-dev] [PATCH v3 " Tomasz Cel
2018-10-08 17:16 ` [dpdk-dev] [PATCH v3 1/3] crypto/qat: add support AES-CMAC Tomasz Cel
2018-10-08 17:16 ` [dpdk-dev] [PATCH v3 2/3] test/qat: test for AES-CMAC Tomasz Cel
2018-10-08 17:16 ` [dpdk-dev] [PATCH v3 3/3] doc/qat: update AES-CMAC documentation Tomasz Cel
2018-10-09 14:37 ` Trahe, Fiona [this message]
2018-10-09 16:08 ` [dpdk-dev] [PATCH v4 0/3] add AES-CMAC support Tomasz Cel
2018-10-09 16:08 ` [dpdk-dev] [PATCH v4 1/3] crypto/qat: add support AES-CMAC Tomasz Cel
2018-10-09 16:08 ` [dpdk-dev] [PATCH v4 2/3] test/qat: test for AES-CMAC Tomasz Cel
2018-10-09 16:08 ` [dpdk-dev] [PATCH v4 3/3] doc/qat: update AES-CMAC documentation Tomasz Cel
2018-10-09 16:25 ` [dpdk-dev] [PATCH v4 0/3] add AES-CMAC support Trahe, Fiona
2018-10-10 10:59 ` 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=348A99DA5F5B7549AA880327E580B43589646B6A@IRSMSX101.ger.corp.intel.com \
--to=fiona.trahe@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=dev@dpdk.org \
--cc=marko.kovacevic@intel.com \
--cc=mattias.ronnblom@ericsson.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).