[dpdk-stable] patch 'doc: fix number of failsafe sub-devices' has been queued to stable release 19.11.3

[luca.boccassi at gmail.com]

Hi,

FYI, your patch has been queued to stable release 19.11.3

Note it hasn't been pushed to http://dpdk.org/browse/dpdk-stable yet.
It will be pushed if I get no objections before 05/21/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 194ca60cde179bae1f88b4eb87fddac20c60cfae Mon Sep 17 00:00:00 2001
From: Gaetan Rivet <grive at u256.net>
Date: Sat, 22 Feb 2020 01:14:40 +0100
Subject: [PATCH] doc: fix number of failsafe sub-devices

[ upstream commit c4169faf9dab18d164557e2b52f7ba1e9d6b768f ]

Supporting more than 2 sub-device is a remnant from earlier fail-safe
design, that was never actually published.

Fixes: a46f8d584eb8 ("net/failsafe: add fail-safe PMD")

Signed-off-by: Gaetan Rivet <grive at u256.net>
---
 doc/guides/nics/fail_safe.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/guides/nics/fail_safe.rst b/doc/guides/nics/fail_safe.rst
index 6c02d7ef6d..60bbf40f7f 100644
--- a/doc/guides/nics/fail_safe.rst
+++ b/doc/guides/nics/fail_safe.rst
@@ -49,7 +49,7 @@ The Fail-safe PMD can be used like most other DPDK virtual devices, by passing a
 ``--vdev`` parameter to the EAL when starting the application. The device name
 must start with the *net_failsafe* prefix, followed by numbers or letters. This
 name must be unique for each device. Each fail-safe instance must have at least one
-sub-device, up to ``RTE_MAX_ETHPORTS-1``.
+sub-device, and at most two.
 
 A sub-device can be any legal DPDK device, including possibly another fail-safe
 instance.
-- 
2.20.1

---
  Diff of the applied patch vs upstream commit (please double-check if non-empty:
---
--- -	2020-05-19 13:56:19.838172744 +0100
+++ 0025-doc-fix-number-of-failsafe-sub-devices.patch	2020-05-19 13:56:18.207501603 +0100
@@ -1,13 +1,14 @@
-From c4169faf9dab18d164557e2b52f7ba1e9d6b768f Mon Sep 17 00:00:00 2001
+From 194ca60cde179bae1f88b4eb87fddac20c60cfae Mon Sep 17 00:00:00 2001
 From: Gaetan Rivet <grive at u256.net>
 Date: Sat, 22 Feb 2020 01:14:40 +0100
 Subject: [PATCH] doc: fix number of failsafe sub-devices
 
+[ upstream commit c4169faf9dab18d164557e2b52f7ba1e9d6b768f ]
+
 Supporting more than 2 sub-device is a remnant from earlier fail-safe
 design, that was never actually published.
 
 Fixes: a46f8d584eb8 ("net/failsafe: add fail-safe PMD")
-Cc: stable at dpdk.org
 
 Signed-off-by: Gaetan Rivet <grive at u256.net>
 ---
@@ -15,7 +16,7 @@
  1 file changed, 1 insertion(+), 1 deletion(-)
 
 diff --git a/doc/guides/nics/fail_safe.rst b/doc/guides/nics/fail_safe.rst
-index 3ce2f8bee3..b4a92f663b 100644
+index 6c02d7ef6d..60bbf40f7f 100644
 --- a/doc/guides/nics/fail_safe.rst
 +++ b/doc/guides/nics/fail_safe.rst
 @@ -49,7 +49,7 @@ The Fail-safe PMD can be used like most other DPDK virtual devices, by passing a
@@ -25,8 +26,8 @@
 -sub-device, up to ``RTE_MAX_ETHPORTS-1``.
 +sub-device, and at most two.
  
- A sub-device can be any DPDK device, including possibly another fail-safe device.
- 
+ A sub-device can be any legal DPDK device, including possibly another fail-safe
+ instance.
 -- 
 2.20.1