[dpdk-stable] patch 'doc: fix reference to master process' has been queued to stable release 19.11.4

[luca.boccassi at gmail.com]

Hi,

FYI, your patch has been queued to stable release 19.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 08/12/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 c24a4d83a35e4498173f8fd2c798eb845b9b6417 Mon Sep 17 00:00:00 2001
From: Stephen Hemminger <stephen at networkplumber.org>
Date: Thu, 6 Aug 2020 10:19:44 -0700
Subject: [PATCH] doc: fix reference to master process

[ upstream commit ad18592bc0e064873265952805aaaf60af91cbe6 ]

Correct terminolgy here is primary process.
This is a bug in original doc.

Fixes: fc1f2750a3ec ("doc: programmers guide")

Signed-off-by: Stephen Hemminger <stephen at networkplumber.org>
Acked-by: Anatoly Burakov <anatoly.burakov at intel.com>
Acked-by: John McNamara <john.mcnamara at intel.com>
---
 doc/guides/prog_guide/thread_safety_dpdk_functions.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/guides/prog_guide/thread_safety_dpdk_functions.rst b/doc/guides/prog_guide/thread_safety_dpdk_functions.rst
index 0f539db2b..5618e25e4 100644
--- a/doc/guides/prog_guide/thread_safety_dpdk_functions.rst
+++ b/doc/guides/prog_guide/thread_safety_dpdk_functions.rst
@@ -61,8 +61,8 @@ rather than subsequently in the forwarding threads.
 However, the DPDK performs checks to ensure that libraries are only initialized once.
 If initialization is attempted more than once, an error is returned.
 
-In the multi-process case, the configuration information of shared memory will only be initialized by the master process.
-Thereafter, both master and secondary processes can allocate/release any objects of memory that finally rely on rte_malloc or memzones.
+In the multi-process case, the configuration information of shared memory will only be initialized by the primary process.
+Thereafter, both primary and secondary processes can allocate/release any objects of memory that finally rely on rte_malloc or memzones.
 
 Interrupt Thread
 ----------------
-- 
2.20.1

---
  Diff of the applied patch vs upstream commit (please double-check if non-empty:
---
--- -	2020-08-10 12:04:18.430260438 +0100
+++ 0002-doc-fix-reference-to-master-process.patch	2020-08-10 12:04:18.347555497 +0100
@@ -1,13 +1,14 @@
-From ad18592bc0e064873265952805aaaf60af91cbe6 Mon Sep 17 00:00:00 2001
+From c24a4d83a35e4498173f8fd2c798eb845b9b6417 Mon Sep 17 00:00:00 2001
 From: Stephen Hemminger <stephen at networkplumber.org>
 Date: Thu, 6 Aug 2020 10:19:44 -0700
 Subject: [PATCH] doc: fix reference to master process
 
+[ upstream commit ad18592bc0e064873265952805aaaf60af91cbe6 ]
+
 Correct terminolgy here is primary process.
 This is a bug in original doc.
 
 Fixes: fc1f2750a3ec ("doc: programmers guide")
-Cc: stable at dpdk.org
 
 Signed-off-by: Stephen Hemminger <stephen at networkplumber.org>
 Acked-by: Anatoly Burakov <anatoly.burakov at intel.com>