From: Pablo de Lara <pablo.de.lara.guarch@intel.com>
To: stable@dpdk.org
Cc: bluca@debian.org, Pablo de Lara <pablo.de.lara.guarch@intel.com>
Subject: [dpdk-stable] [PATCH] crypto/qat: fix SHA512-HMAC supported key size
Date: Thu, 2 Nov 2017 09:53:27 +0000 [thread overview]
Message-ID: <20171102095327.6678-1-pablo.de.lara.guarch@intel.com> (raw)
This commit fixes a backported commit which introduced
an in incorrect value for the maximum supported key size
for SHA512-HMAC.
Fixes: c2cdabf725dc ("crypto/qat: fix HMAC supported key sizes")
Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
---
drivers/crypto/qat/qat_crypto.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/crypto/qat/qat_crypto.c b/drivers/crypto/qat/qat_crypto.c
index f7fcece..8b830b8 100644
--- a/drivers/crypto/qat/qat_crypto.c
+++ b/drivers/crypto/qat/qat_crypto.c
@@ -162,7 +162,7 @@ static const struct rte_cryptodev_capabilities qat_pmd_capabilities[] = {
.key_size = {
.min = 1,
.max = 128,
- .increment = 128
+ .increment = 1
},
.digest_size = {
.min = 64,
--
2.9.4
next reply other threads:[~2017-11-02 9:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-02 9:53 Pablo de Lara [this message]
2017-11-02 12:53 ` Luca Boccassi
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=20171102095327.6678-1-pablo.de.lara.guarch@intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=bluca@debian.org \
--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).