From: Yuanhan Liu <yuanhan.liu@linux.intel.com>
To: Deepak Kumar Jain <deepak.k.jain@intel.com>
Cc: dpdk stable <stable@dpdk.org>, Fiona Trahe <fiona.trahe@intel.com>
Subject: [dpdk-stable] patch 'crypto/null: fix key size increment value' has been queued to stable release 16.07.1
Date: Wed, 12 Oct 2016 14:44:24 +0800 [thread overview]
Message-ID: <57fddbc8.1NuJI4Xqw5qI/Ic4%yuanhan.liu@linux.intel.com> (raw)
Hi,
FYI, your patch has been queued to stable release 16.07.1
Note it hasn't been pushed to http://dpdk.org/browse/dpdk-stable
yet. It will be pushed if I get no objections before this Friday.
So please shutout if anyone has objections.
Thanks.
--yliu
---
>From d473557ed053347c08e307fbe6d79cf4bf65e708 Mon Sep 17 00:00:00 2001
From: Deepak Kumar Jain <deepak.k.jain@intel.com>
Date: Fri, 16 Sep 2016 11:49:34 +0100
Subject: [PATCH] crypto/null: fix key size increment value
[ upstream commit 6bc430031883c018e49b092a415b2c40ba073715 ]
This patch fixes the values of increment in key size.
Fixes: 94b0ad8e0aa5 ("null_crypto: add driver for null crypto operations")
Signed-off-by: Deepak Kumar Jain <deepak.k.jain@intel.com>
Acked-by: Fiona Trahe <fiona.trahe@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,
--
1.9.0
reply other threads:[~2016-10-12 6:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=57fddbc8.1NuJI4Xqw5qI/Ic4%yuanhan.liu@linux.intel.com \
--to=yuanhan.liu@linux.intel.com \
--cc=deepak.k.jain@intel.com \
--cc=fiona.trahe@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).