On Wed, Apr 11, 2018 at 08:50:56PM -0300, Flavio Leitner wrote:
> Create a document to describe the how it works and known
> limitations and update the NEWS accordingly.
>
> Signed-off-by: Flavio Leitner <f...@sysclose.org>
Thanks! I folded in the following to make "checkpatch" and "make"
happy, and then I applied this to master.
--8<--------------------------cut here-------------------------->8--
diff --git a/Documentation/automake.mk b/Documentation/automake.mk
index 93cf3a11be57..c05a2313a5b8 100644
--- a/Documentation/automake.mk
+++ b/Documentation/automake.mk
@@ -40,6 +40,7 @@ DOC_SOURCE = \
Documentation/topics/high-availability.rst \
Documentation/topics/integration.rst \
Documentation/topics/language-bindings.rst \
+ Documentation/topics/networking-namespaces.rst \
Documentation/topics/openflow.rst \
Documentation/topics/ovn-news-2.8.rst \
Documentation/topics/ovsdb-replication.rst \
diff --git a/Documentation/topics/index.rst b/Documentation/topics/index.rst
index 13b6d8abbb30..fa7f0a2fb089 100644
--- a/Documentation/topics/index.rst
+++ b/Documentation/topics/index.rst
@@ -42,6 +42,7 @@ OVS
porting
openflow
bonding
+ networking-namespaces
ovsdb-replication
dpdk/index
windows
diff --git a/Documentation/topics/networking-namespaces.rst
b/Documentation/topics/networking-namespaces.rst
index 96589b513080..5c265cd0247b 100644
--- a/Documentation/topics/networking-namespaces.rst
+++ b/Documentation/topics/networking-namespaces.rst
@@ -66,4 +66,3 @@ setting MTU, lacks the proper API in the kernel, so they
remain unsupported.
In most use cases that needs to move ports to another networking namespaces
should use veth pairs instead because it offers a cleaner and more robust
solution with no noticeable performance penalty.
-
_______________________________________________
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev
