patch 'doc: fix number of leading spaces in hns3 guide' has been queued to stable release 22.11.3

[Xueming Li]

Hi,

FYI, your patch has been queued to stable release 22.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 08/11/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://git.dpdk.org/dpdk-stable/log/?h=22.11-staging

This queued commit can be viewed at:
https://git.dpdk.org/dpdk-stable/commit/?h=22.11-staging&id=7a44cac46c71c87928c34f401641f74788d7019e

Thanks.

Xueming Li <xuemingl at nvidia.com>

---
>From 7a44cac46c71c87928c34f401641f74788d7019e Mon Sep 17 00:00:00 2001
From: Dongdong Liu <liudongdong3 at huawei.com>
Date: Fri, 30 Jun 2023 15:37:37 +0800
Subject: [PATCH] doc: fix number of leading spaces in hns3 guide
Cc: Xueming Li <xuemingl at nvidia.com>

[ upstream commit 620cd2d5ac5a6d7de750a4827e2840209a1b0cbb ]

The current description of 'mbx_time_limit_ms' has three spaces
at the beginning. Use two spaces to keep the same style with other
places and add a blank line after '::'.

Fixes: 2fc3e696a7f1 ("net/hns3: add runtime config for mailbox limit time")

Signed-off-by: Dongdong Liu <liudongdong3 at huawei.com>
---
 doc/guides/nics/hns3.rst | 34 ++++++++++++++++++----------------
 1 file changed, 18 insertions(+), 16 deletions(-)

diff --git a/doc/guides/nics/hns3.rst b/doc/guides/nics/hns3.rst
index 8a6998fd65..6fbd4320ef 100644
--- a/doc/guides/nics/hns3.rst
+++ b/doc/guides/nics/hns3.rst
@@ -82,7 +82,7 @@ Runtime Config Options
 
   For example::
 
-  -a 0000:7d:00.0,rx_func_hint=simple
+    -a 0000:7d:00.0,rx_func_hint=simple
 
 - ``tx_func_hint`` (default ``none``)
 
@@ -103,7 +103,7 @@ Runtime Config Options
 
   For example::
 
-  -a 0000:7d:00.0,tx_func_hint=common
+    -a 0000:7d:00.0,tx_func_hint=common
 
 - ``dev_caps_mask`` (default ``0``)
 
@@ -116,22 +116,24 @@ Runtime Config Options
 
   For example::
 
-  -a 0000:7d:00.0,dev_caps_mask=0xF
+    -a 0000:7d:00.0,dev_caps_mask=0xF
 
 - ``mbx_time_limit_ms`` (default ``500``)
-   Used to define the mailbox time limit by user.
-   Current, the max waiting time for MBX response is 500ms, but in
-   some scenarios, it is not enough. Since it depends on the response
-   of the kernel mode driver, and its response time is related to the
-   scheduling of the system. In this special scenario, most of the
-   cores are isolated, and only a few cores are used for system
-   scheduling. When a large number of services are started, the
-   scheduling of the system will be very busy, and the reply of the
-   mbx message will time out, which will cause our PMD initialization
-   to fail. So provide access to set mailbox time limit for user.
-
-   For example::
-   -a 0000:7d:00.0,mbx_time_limit_ms=600
+
+  Used to define the mailbox time limit by user.
+  Current, the max waiting time for MBX response is 500ms, but in
+  some scenarios, it is not enough. Since it depends on the response
+  of the kernel mode driver, and its response time is related to the
+  scheduling of the system. In this special scenario, most of the
+  cores are isolated, and only a few cores are used for system
+  scheduling. When a large number of services are started, the
+  scheduling of the system will be very busy, and the reply of the
+  mbx message will time out, which will cause our PMD initialization
+  to fail. So provide access to set mailbox time limit for user.
+
+  For example::
+
+    -a 0000:7d:00.0,mbx_time_limit_ms=600
 
 Link status event Pre-conditions
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-- 
2.25.1

---
  Diff of the applied patch vs upstream commit (please double-check if non-empty:
---
--- -	2023-08-09 21:51:19.825621700 +0800
+++ 0064-doc-fix-number-of-leading-spaces-in-hns3-guide.patch	2023-08-09 21:51:18.204352000 +0800
@@ -1 +1 @@
-From 620cd2d5ac5a6d7de750a4827e2840209a1b0cbb Mon Sep 17 00:00:00 2001
+From 7a44cac46c71c87928c34f401641f74788d7019e Mon Sep 17 00:00:00 2001
@@ -4,0 +5,3 @@
+Cc: Xueming Li <xuemingl at nvidia.com>
+
+[ upstream commit 620cd2d5ac5a6d7de750a4827e2840209a1b0cbb ]
@@ -11 +13,0 @@
-Cc: stable at dpdk.org
@@ -19 +21 @@
-index 11cbc992e7..ee774639d3 100644
+index 8a6998fd65..6fbd4320ef 100644
@@ -22 +24 @@
-@@ -93,7 +93,7 @@ Runtime Configuration
+@@ -82,7 +82,7 @@ Runtime Config Options
@@ -31 +33 @@
-@@ -114,7 +114,7 @@ Runtime Configuration
+@@ -103,7 +103,7 @@ Runtime Config Options
@@ -40 +42 @@
-@@ -127,22 +127,24 @@ Runtime Configuration
+@@ -116,22 +116,24 @@ Runtime Config Options
@@ -77,2 +79,2 @@
- - ``fdir_vlan_match_mode`` (default ``strict``)
- 
+ Link status event Pre-conditions
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~