From: "Trahe, Fiona" <fiona.trahe@intel.com>
To: "Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
"Griffin, John" <john.griffin@intel.com>,
"Jain, Deepak K" <deepak.k.jain@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2 3/3] test: add ZUC test cases for QAT
Date: Thu, 30 Mar 2017 13:36:11 +0000 [thread overview]
Message-ID: <348A99DA5F5B7549AA880327E580B435891D6FB6@IRSMSX101.ger.corp.intel.com> (raw)
In-Reply-To: <1490792659-31544-4-git-send-email-arkadiuszx.kusztal@intel.com>
> -----Original Message-----
> From: Kusztal, ArkadiuszX
> Sent: Wednesday, March 29, 2017 2:04 PM
> To: dev@dpdk.org
> Cc: Trahe, Fiona <fiona.trahe@intel.com>; De Lara Guarch, Pablo
> <pablo.de.lara.guarch@intel.com>; Griffin, John <john.griffin@intel.com>;
> Jain, Deepak K <deepak.k.jain@intel.com>; Kusztal, ArkadiuszX
> <arkadiuszx.kusztal@intel.com>
> Subject: [PATCH v2 3/3] test: add ZUC test cases for QAT
>
> This patch adds ZUC EEA3/EIA3 test cases for QAT crypto
> test suite and consolidate ZUC test vectors into one header file.
>
> Signed-off-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
Acked-by: Fiona Trahe <fiona.trahe@intel.com>
next prev parent reply other threads:[~2017-03-30 13:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-29 13:04 [dpdk-dev] [PATCH v2 0/3] Add ZUC EEA3/EIA3 capability to Intel(R) QuickAssist Technology driver Arek Kusztal
2017-03-29 13:04 ` [dpdk-dev] [PATCH v2 1/3] crypto/qat: refactor capabilities infrastructure Arek Kusztal
2017-03-30 13:34 ` Trahe, Fiona
2017-03-30 21:50 ` De Lara Guarch, Pablo
2017-03-29 13:04 ` [dpdk-dev] [PATCH v2 2/3] crypto/qat: add ZUC EEA3/EIA3 capability Arek Kusztal
2017-03-30 13:35 ` Trahe, Fiona
2017-03-29 13:04 ` [dpdk-dev] [PATCH v2 3/3] test: add ZUC test cases for QAT Arek Kusztal
2017-03-30 13:36 ` Trahe, Fiona [this message]
2017-03-30 21:29 ` De Lara Guarch, Pablo
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=348A99DA5F5B7549AA880327E580B435891D6FB6@IRSMSX101.ger.corp.intel.com \
--to=fiona.trahe@intel.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=deepak.k.jain@intel.com \
--cc=dev@dpdk.org \
--cc=john.griffin@intel.com \
--cc=pablo.de.lara.guarch@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).