From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "Jain, Deepak K" <deepak.k.jain@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v4 0/2] add NULL crypto support in Intel QAT driver
Date: Fri, 16 Sep 2016 21:54:31 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8973C9EA727@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <1474016237-85255-1-git-send-email-deepak.k.jain@intel.com>
> -----Original Message-----
> From: Jain, Deepak K
> Sent: Friday, September 16, 2016 1:57 AM
> To: dev@dpdk.org
> Cc: De Lara Guarch, Pablo; Jain, Deepak K
> Subject: [PATCH v4 0/2] add NULL crypto support in Intel QAT driver
>
> This patchset adds support of NULL crypto in Intel(R) QuickAssist Technology
> driver.
>
> This patchset depends on following patchset:
> "crypto/qat: add aes-sha384-hmac capability to Intel QAT driver"
> (http://dpdk.org/dev/patchwork/patch/15778/)
>
> Deepak Kumar JAIN (2):
> crypto/qat: add NULL capability to Intel QAT driver
> app/test: add test cases for NULL for Intel QAT driver
>
> Changes in v4:
> * Correct increment of key size in capabilities.
>
> Changes in v3:
> * Added information in capability structure.
>
> Changes in v2:
> * Added new feature information in release_16_11.rst file.
>
> app/test/test_cryptodev.c | 10 ++++++
> doc/guides/cryptodevs/qat.rst | 3 +-
> doc/guides/rel_notes/release_16_11.rst | 1 +
> drivers/crypto/qat/qat_adf/qat_algs_build_desc.c | 2 ++
> drivers/crypto/qat/qat_crypto.c | 45 ++++++++++++++++++++++++
> 5 files changed, 60 insertions(+), 1 deletion(-)
>
> --
> 2.5.5
Applied to dpdk-next-crypto.
Thanks,
Pablo
prev parent reply other threads:[~2016-09-16 21:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-18 13:34 [dpdk-dev] [PATCH " Deepak Kumar Jain
2016-08-18 13:34 ` [dpdk-dev] [PATCH 1/2] crypto/qat: add NULL capability to " Deepak Kumar Jain
2016-08-18 13:34 ` [dpdk-dev] [PATCH 2/2] app/test: add test cases for NULL for " Deepak Kumar Jain
2016-09-07 18:05 ` [dpdk-dev] [PATCH 0/2] add NULL crypto support in " De Lara Guarch, Pablo
2016-09-07 19:33 ` Jain, Deepak K
2016-09-12 20:00 ` [dpdk-dev] [PATCH v2 " Deepak Kumar Jain
2016-09-12 20:00 ` [dpdk-dev] [PATCH v2 1/2] crypto/qat: add NULL capability to " Deepak Kumar Jain
2016-09-12 20:00 ` [dpdk-dev] [PATCH v2 2/2] app/test: add test cases for NULL for " Deepak Kumar Jain
2016-09-13 8:59 ` [dpdk-dev] [PATCH v3 0/2] add NULL crypto support in " Deepak Kumar Jain
2016-09-13 8:59 ` [dpdk-dev] [PATCH v3 1/2] crypto/qat: add NULL capability to " Deepak Kumar Jain
2016-09-15 13:34 ` Trahe, Fiona
2016-09-16 1:43 ` De Lara Guarch, Pablo
2016-09-13 8:59 ` [dpdk-dev] [PATCH v3 2/2] app/test: add test cases for NULL for " Deepak Kumar Jain
2016-09-15 13:48 ` Trahe, Fiona
2016-09-16 8:57 ` [dpdk-dev] [PATCH v4 0/2] add NULL crypto support in " Deepak Kumar Jain
2016-09-16 8:57 ` [dpdk-dev] [PATCH v4 1/2] crypto/qat: add NULL capability to " Deepak Kumar Jain
2016-09-16 8:57 ` [dpdk-dev] [PATCH v4 2/2] app/test: add test cases for NULL for " Deepak Kumar Jain
2016-09-16 21:54 ` De Lara Guarch, Pablo [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=E115CCD9D858EF4F90C690B0DCB4D8973C9EA727@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=deepak.k.jain@intel.com \
--cc=dev@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).