patch 'doc: fix LPM support in l3forward guide' has been queued to stable release 21.11.4

[Kevin Traynor <ktraynor@redhat.com>]

Hi,

FYI, your patch has been queued to stable release 21.11.4

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

This queued commit can be viewed at:
https://github.com/kevintraynor/dpdk-stable/commit/34934b2b198e36c19eb3d021a60bb9bcb91db2dd

Thanks.

Kevin

---
From 34934b2b198e36c19eb3d021a60bb9bcb91db2dd Mon Sep 17 00:00:00 2001
From: Kamalakshitha Aligeri <kamalakshitha.aligeri@arm.com>
Date: Mon, 6 Mar 2023 16:25:07 +0000
Subject: [PATCH] doc: fix LPM support in l3forward guide

[ upstream commit 2bf48044dca1892e571fd4964eecaacf6cb0c1c2 ]

LPM based lookup supports both IPv4 and IPv6 forwarding.

Fixes: 6a094e328598 ("examples/l3fwd: implement FIB lookup method")

Signed-off-by: Kamalakshitha Aligeri <kamalakshitha.aligeri@arm.com>
Reviewed-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
Reviewed-by: Ruifeng Wang <ruifeng.wang@arm.com>
Acked-by: Konstantin Ananyev <konstantin.ananyev@huawei.com>
---
 doc/guides/sample_app_ug/l3_forward.rst | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/doc/guides/sample_app_ug/l3_forward.rst b/doc/guides/sample_app_ug/l3_forward.rst
index 6d7d7c5cc1..9fb44e2c23 100644
--- a/doc/guides/sample_app_ug/l3_forward.rst
+++ b/doc/guides/sample_app_ug/l3_forward.rst
@@ -45,7 +45,6 @@ The set of LPM and FIB rules used by the application is statically configured
 and loaded into the LPM or FIB object at initialization time.
 
-In the sample application, hash-based and FIB-based forwarding supports
+In the sample application, hash-based, LPM-based, FIB-based and ACL-based forwarding supports
 both IPv4 and IPv6.
-LPM-based forwarding supports IPv4 only.
 
 Compiling the Application
-- 
2.39.2

---
  Diff of the applied patch vs upstream commit (please double-check if non-empty:
---
--- -	2023-03-22 10:30:08.395236348 +0000
+++ 0019-doc-fix-LPM-support-in-l3forward-guide.patch	2023-03-22 10:30:07.932866584 +0000
@@ -1 +1 @@
-From 2bf48044dca1892e571fd4964eecaacf6cb0c1c2 Mon Sep 17 00:00:00 2001
+From 34934b2b198e36c19eb3d021a60bb9bcb91db2dd Mon Sep 17 00:00:00 2001
@@ -5,0 +6,2 @@
+[ upstream commit 2bf48044dca1892e571fd4964eecaacf6cb0c1c2 ]
+
@@ -9 +10,0 @@
-Cc: stable@dpdk.org
@@ -20 +21 @@
-index 94b22da01e..1cc2c1dd1d 100644
+index 6d7d7c5cc1..9fb44e2c23 100644
@@ -23,2 +24,2 @@
-@@ -57,7 +57,6 @@ The 5-tuple syntax consists of a source IP address, a destination IP address,
- a source port, a destination port and a protocol identifier.
+@@ -45,7 +45,6 @@ The set of LPM and FIB rules used by the application is statically configured
+ and loaded into the LPM or FIB object at initialization time.
@@ -26 +27 @@
--In the sample application, hash-based, FIB-based and ACL-based forwarding supports
+-In the sample application, hash-based and FIB-based forwarding supports
@@ -30 +30,0 @@
- During the initialization phase route rules for IPv4 and IPv6 are read from rule files.
@@ -31,0 +32 @@
+ Compiling the Application