From: Deepak Kumar Jain <deepak.k.jain@intel.com>
To: dev@dpdk.org
Cc: pablo.de.lara.guarch@intel.com,
Deepak Kumar Jain <deepak.k.jain@intel.com>
Subject: [dpdk-dev] [PATCH] crypto/null: fix key size increment value
Date: Fri, 16 Sep 2016 11:49:34 +0100 [thread overview]
Message-ID: <1474022974-91860-1-git-send-email-deepak.k.jain@intel.com> (raw)
This patch fixes the values of increment in key size.
Fixes: 94b0ad8e0a ("null_crypto_pmd: PMD to support null crypto
operations")
Signed-off-by: Deepak Kumar Jain <deepak.k.jain@intel.com>
---
drivers/crypto/null/null_crypto_pmd_ops.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/crypto/null/null_crypto_pmd_ops.c b/drivers/crypto/null/null_crypto_pmd_ops.c
index cf1a519..26ff631 100644
--- a/drivers/crypto/null/null_crypto_pmd_ops.c
+++ b/drivers/crypto/null/null_crypto_pmd_ops.c
@@ -70,7 +70,7 @@ static const struct rte_cryptodev_capabilities null_crypto_pmd_capabilities[] =
.key_size = {
.min = 0,
.max = 0,
- .increment = 8
+ .increment = 0
},
.iv_size = {
.min = 0,
--
2.5.5
next reply other threads:[~2016-09-16 10:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-16 10:49 Deepak Kumar Jain [this message]
2016-09-16 15:55 ` Trahe, Fiona
2016-09-16 21:34 ` 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=1474022974-91860-1-git-send-email-deepak.k.jain@intel.com \
--to=deepak.k.jain@intel.com \
--cc=dev@dpdk.org \
--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).