From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Trahe, Fiona" <fiona.trahe@intel.com>,
"Griffin, John" <john.griffin@intel.com>,
"Jain, Deepak K" <deepak.k.jain@intel.com>
Subject: Re: [dpdk-dev] [PATCH 1/2] crypto/qat: add ZUC EEA3 cipher capability
Date: Wed, 1 Mar 2017 20:33:40 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D897476E6157@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <1488354962-12144-2-git-send-email-arkadiuszx.kusztal@intel.com>
Hi Arek,
> -----Original Message-----
> From: Kusztal, ArkadiuszX
> Sent: Wednesday, March 01, 2017 7:56 AM
> To: dev@dpdk.org
> Cc: Trahe, Fiona; De Lara Guarch, Pablo; Griffin, John; Jain, Deepak K;
> Kusztal, ArkadiuszX
> Subject: [PATCH 1/2] crypto/qat: add ZUC EEA3 cipher capability
>
> This commit adds ZUC EEA3 cipher capability to Intel(R) QuickAssist
> Technology driver
>
> Signed-off-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
> ---
> doc/guides/cryptodevs/qat.rst | 2 +
> drivers/crypto/qat/qat_adf/qat_algs.h | 11 ++-
> drivers/crypto/qat/qat_adf/qat_algs_build_desc.c | 97
> ++++++++++++++++++++----
> drivers/crypto/qat/qat_crypto.c | 34 ++++++++-
> 4 files changed, 125 insertions(+), 19 deletions(-)
Could you update the supported algorithm matrices, to reflect this change?
Also, add the change in the release notes.
Thanks,
Pablo
next prev parent reply other threads:[~2017-03-01 20:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-01 7:56 [dpdk-dev] [PATCH 0/2] Add ZUC EEA3 capability to Intel(R) QuickAssist Technology driver Arek Kusztal
2017-03-01 7:56 ` [dpdk-dev] [PATCH 1/2] crypto/qat: add ZUC EEA3 cipher capability Arek Kusztal
2017-03-01 12:30 ` Trahe, Fiona
2017-03-01 20:33 ` De Lara Guarch, Pablo [this message]
2017-03-03 6:23 ` Yang, GangX
2017-03-01 7:56 ` [dpdk-dev] [PATCH 2/2] app/test: add ZUC EEA3 test cases to QAT test suite Arek Kusztal
2017-03-01 12:31 ` Trahe, Fiona
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=E115CCD9D858EF4F90C690B0DCB4D897476E6157@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=deepak.k.jain@intel.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--cc=john.griffin@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).