[dpdk-stable] patch 'test/crypto: fix device number' has been queued to stable release 19.11.6

luca.boccassi at gmail.com luca.boccassi at gmail.com
Wed Oct 28 11:45:02 CET 2020


Hi,

FYI, your patch has been queued to stable release 19.11.6

Note it hasn't been pushed to http://dpdk.org/browse/dpdk-stable yet.
It will be pushed if I get no objections before 10/30/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.

Thanks.

Luca Boccassi

---
>From a0a9359d0350e69139958b0c5b34e1d4a2203385 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>
---
 app/test/test_cryptodev.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/app/test/test_cryptodev.c b/app/test/test_cryptodev.c
index fd1056dec1..75d35c6582 100644
--- a/app/test/test_cryptodev.c
+++ b/app/test/test_cryptodev.c
@@ -643,7 +643,7 @@ test_device_configure_invalid_dev_id(void)
 			"Need at least %d devices for test", 1);
 
 	/* 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 */
 	rte_cryptodev_stop(dev_id);
-- 
2.20.1

---
  Diff of the applied patch vs upstream commit (please double-check if non-empty:
---
--- -	2020-10-28 10:35:16.172271556 +0000
+++ 0143-test-crypto-fix-device-number.patch	2020-10-28 10:35:11.724833262 +0000
@@ -1,14 +1,15 @@
-From ff56727b4fae5841ec0c214223e71e78511b5687 Mon Sep 17 00:00:00 2001
+From a0a9359d0350e69139958b0c5b34e1d4a2203385 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")
-Cc: stable at dpdk.org
 
 Signed-off-by: Ankur Dwivedi <adwivedi at marvell.com>
 Acked-by: Fan Zhang <roy.fan.zhang at intel.com>
@@ -17,10 +18,10 @@
  1 file changed, 1 insertion(+), 1 deletion(-)
 
 diff --git a/app/test/test_cryptodev.c b/app/test/test_cryptodev.c
-index 153d001194..162c21dd88 100644
+index fd1056dec1..75d35c6582 100644
 --- a/app/test/test_cryptodev.c
 +++ b/app/test/test_cryptodev.c
-@@ -755,7 +755,7 @@ test_device_configure_invalid_dev_id(void)
+@@ -643,7 +643,7 @@ test_device_configure_invalid_dev_id(void)
  			"Need at least %d devices for test", 1);
  
  	/* valid dev_id values */


More information about the stable mailing list