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>,
"Doherty, Declan" <declan.doherty@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH v2 3/3] crypto/qat: fix iv size in PMD capabilities
Date: Fri, 6 Jan 2017 10:31:28 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D897476BF40E@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <1482481493-4369-4-git-send-email-arkadiuszx.kusztal@intel.com>
CC'ing stable mailing list.
> -----Original Message-----
> From: Kusztal, ArkadiuszX
> Sent: Friday, December 23, 2016 8:25 AM
> To: dev@dpdk.org
> Cc: Trahe, Fiona; De Lara Guarch, Pablo; Griffin, John; Jain, Deepak K;
> Doherty, Declan; Kusztal, ArkadiuszX
> Subject: [PATCH v2 3/3] crypto/qat: fix iv size in PMD capabilities
>
> This patch sets iv size in qat PMD to 12 bytes to be
> conformant with nist SP800-38D.
>
> Fixes: 26c2e4ad5ad4 ("cryptodev: add capabilities discovery")
>
> Signed-off-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
> ---
> drivers/crypto/qat/qat_crypto.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/crypto/qat/qat_crypto.c
> b/drivers/crypto/qat/qat_crypto.c
> index fa78c60..0b714ad 100644
> --- a/drivers/crypto/qat/qat_crypto.c
> +++ b/drivers/crypto/qat/qat_crypto.c
> @@ -303,8 +303,8 @@ static const struct rte_cryptodev_capabilities
> qat_pmd_capabilities[] = {
> .increment = 8
> },
> .iv_size = {
> - .min = 16,
> - .max = 16,
> + .min = 12,
> + .max = 12,
> .increment = 0
> }
> }, }
> --
> 2.1.0
next prev parent reply other threads:[~2017-01-06 10:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1482481493-4369-1-git-send-email-arkadiuszx.kusztal@intel.com>
[not found] ` <1482481493-4369-2-git-send-email-arkadiuszx.kusztal@intel.com>
2017-01-06 10:27 ` [dpdk-stable] [PATCH v2 1/3] crypto/aesni_gcm: fix J0 padding bytes for GCM De Lara Guarch, Pablo
[not found] ` <1482481493-4369-4-git-send-email-arkadiuszx.kusztal@intel.com>
2017-01-06 10:31 ` De Lara Guarch, Pablo [this message]
[not found] ` <1482481493-4369-3-git-send-email-arkadiuszx.kusztal@intel.com>
2017-01-06 10:31 ` [dpdk-stable] [PATCH v2 2/3] crypto/aesni_gcm: fix iv size in PMD capabilities 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=E115CCD9D858EF4F90C690B0DCB4D897476BF40E@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=declan.doherty@intel.com \
--cc=deepak.k.jain@intel.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--cc=john.griffin@intel.com \
--cc=stable@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).