[dpdk-stable] patch 'test/crypto: fix device number' has been queued to LTS release 18.11.11
Kevin Traynor
ktraynor at redhat.com
Thu Nov 5 13:40:10 CET 2020
Hi,
FYI, your patch has been queued to LTS release 18.11.11
Note it hasn't been pushed to http://dpdk.org/browse/dpdk-stable yet.
It will be pushed if I get no objections before 11/10/20. So please
shout if anyone has objections.
Also note that after the patch there's a diff of the upstream commit vs the
patch applied to the branch. This will indicate if there was any rebasing
needed to apply to the stable branch. If there were code changes for rebasing
(ie: not only metadata diffs), please double check that the rebase was
correctly done.
Queued patches are on a temporary branch at:
https://github.com/kevintraynor/dpdk-stable-queue
This queued commit can be viewed at:
https://github.com/kevintraynor/dpdk-stable-queue/commit/067c9dc1c177df625547465e619eaa4472f40a7a
Thanks.
Kevin.
---
>From 067c9dc1c177df625547465e619eaa4472f40a7a Mon Sep 17 00:00:00 2001
From: Ankur Dwivedi <adwivedi at marvell.com>
Date: Thu, 30 Jul 2020 16:50:17 +0530
Subject: [PATCH] test/crypto: fix device number
[ upstream commit ff56727b4fae5841ec0c214223e71e78511b5687 ]
In testsuite_setup(), ts_params is configured for first valid device.
The same device should be used as valid device in
test_device_configure_invalid_dev_id test case.
Fixes: 202d375c60bc ("app/test: add cryptodev unit and performance tests")
Signed-off-by: Ankur Dwivedi <adwivedi at marvell.com>
Acked-by: Fan Zhang <roy.fan.zhang at intel.com>
---
test/test/test_cryptodev.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/test/test/test_cryptodev.c b/test/test/test_cryptodev.c
index e13c454a43..210507eb8a 100644
--- a/test/test/test_cryptodev.c
+++ b/test/test/test_cryptodev.c
@@ -598,5 +598,5 @@ test_device_configure_invalid_dev_id(void)
/* valid dev_id values */
- dev_id = ts_params->valid_devs[ts_params->valid_dev_count - 1];
+ dev_id = ts_params->valid_devs[0];
/* Stop the device in case it's started so it can be configured */
--
2.26.2
---
Diff of the applied patch vs upstream commit (please double-check if non-empty:
---
--- - 2020-11-05 12:38:55.699547467 +0000
+++ 0063-test-crypto-fix-device-number.patch 2020-11-05 12:38:54.268896041 +0000
@@ -1 +1 @@
-From ff56727b4fae5841ec0c214223e71e78511b5687 Mon Sep 17 00:00:00 2001
+From 067c9dc1c177df625547465e619eaa4472f40a7a Mon Sep 17 00:00:00 2001
@@ -5,0 +6,2 @@
+[ upstream commit ff56727b4fae5841ec0c214223e71e78511b5687 ]
+
@@ -11 +12,0 @@
-Cc: stable at dpdk.org
@@ -16 +17 @@
- app/test/test_cryptodev.c | 2 +-
+ test/test/test_cryptodev.c | 2 +-
@@ -19,5 +20,5 @@
-diff --git a/app/test/test_cryptodev.c b/app/test/test_cryptodev.c
-index 153d001194..162c21dd88 100644
---- a/app/test/test_cryptodev.c
-+++ b/app/test/test_cryptodev.c
-@@ -756,5 +756,5 @@ test_device_configure_invalid_dev_id(void)
+diff --git a/test/test/test_cryptodev.c b/test/test/test_cryptodev.c
+index e13c454a43..210507eb8a 100644
+--- a/test/test/test_cryptodev.c
++++ b/test/test/test_cryptodev.c
+@@ -598,5 +598,5 @@ test_device_configure_invalid_dev_id(void)
More information about the stable
mailing list