[dpdk-stable] patch 'doc: remove note on memory mode limitation in multi-process' has been queued to LTS release 18.11.1

[Kevin Traynor <ktraynor@redhat.com>]

Hi,

FYI, your patch has been queued to LTS release 18.11.1

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

Kevin Traynor

---
>From d5936803fb2b62db3d953039eb3c981229f28670 Mon Sep 17 00:00:00 2001
From: Anatoly Burakov <anatoly.burakov@intel.com>
Date: Thu, 6 Dec 2018 09:30:33 +0000
Subject: [PATCH] doc: remove note on memory mode limitation in multi-process

[ upstream commit 41328c404f5023df3dddab5daddad2403c5bb434 ]

Memory mode flags are now shared between primary and secondary
processes, so the in documentation about limitations is no longer
necessary.

Fixes: 64cdfc35aaad ("mem: store memory mode flags in shared config")

Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
---
 doc/guides/prog_guide/env_abstraction_layer.rst | 9 ---------
 1 file changed, 9 deletions(-)

diff --git a/doc/guides/prog_guide/env_abstraction_layer.rst b/doc/guides/prog_guide/env_abstraction_layer.rst
index 8b5d050c7..426acfc28 100644
--- a/doc/guides/prog_guide/env_abstraction_layer.rst
+++ b/doc/guides/prog_guide/env_abstraction_layer.rst
@@ -148,13 +148,4 @@ A default validator callback is provided by EAL, which can be enabled with a
 of memory that can be used by DPDK application.
 
-.. note::
-
-    In multiprocess scenario, all related processes (i.e. primary process, and
-    secondary processes running with the same prefix) must be in the same memory
-    modes. That is, if primary process is run in dynamic memory mode, all of its
-    secondary processes must be run in the same mode. The same is applicable to
-    ``--single-file-segments`` command-line option - both primary and secondary
-    processes must shared this mode.
-
 + Legacy memory mode
 
-- 
2.19.0

---
  Diff of the applied patch vs upstream commit (please double-check if non-empty:
---
--- -	2019-01-04 13:23:08.304747242 +0000
+++ 0036-doc-remove-note-on-memory-mode-limitation-in-multi-p.patch	2019-01-04 13:23:07.000000000 +0000
@@ -1,14 +1,15 @@
-From 41328c404f5023df3dddab5daddad2403c5bb434 Mon Sep 17 00:00:00 2001
+From d5936803fb2b62db3d953039eb3c981229f28670 Mon Sep 17 00:00:00 2001
 From: Anatoly Burakov <anatoly.burakov@intel.com>
 Date: Thu, 6 Dec 2018 09:30:33 +0000
 Subject: [PATCH] doc: remove note on memory mode limitation in multi-process
 
+[ upstream commit 41328c404f5023df3dddab5daddad2403c5bb434 ]
+
 Memory mode flags are now shared between primary and secondary
 processes, so the in documentation about limitations is no longer
 necessary.
 
 Fixes: 64cdfc35aaad ("mem: store memory mode flags in shared config")
-Cc: stable@dpdk.org
 
 Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
 ---
@@ -16,7 +17,7 @@
  1 file changed, 9 deletions(-)
 
 diff --git a/doc/guides/prog_guide/env_abstraction_layer.rst b/doc/guides/prog_guide/env_abstraction_layer.rst
-index 5aaac0bd2..929d76dba 100644
+index 8b5d050c7..426acfc28 100644
 --- a/doc/guides/prog_guide/env_abstraction_layer.rst
 +++ b/doc/guides/prog_guide/env_abstraction_layer.rst
 @@ -148,13 +148,4 @@ A default validator callback is provided by EAL, which can be enabled with a