Skip to contentSkip to conversation

Move config NET_NS to from net/Kconfig to init/Kconfig

RFC PATCH In review Matt Helsley 3 participants 3 messages Jan 24, 2009 – Jan 26, 2009

Subsystems (2)
Networking Network drivers
lore
Share & tools
lore

Matt Helsley

author
#0 lore raw

RFC PATCH 1/1 Move config NET_NS to from net/Kconfig to init/Kconfig

Make NET_NS available underneath the generic Namespaces config option since all of the other namespace options are there.

Signed-off-by Matt Helsley <[email protected]>
---
 init/Kconfig |    8 ++++++++
 net/Kconfig  |    8 --------
 2 files changed, 8 insertions(+), 8 deletions(-)
init/Kconfig +8 -0
Index: linux-2.6.29-rc1/init/Kconfig
===================================================================
@@ -541,6 +541,14 @@ config PID_NS
 	  Unless you want to work with an experimental feature
 	  say N here.
 
+config NET_NS
+	bool "Network namespace"
+	default n
+	depends on NAMESPACES && EXPERIMENTAL && NET
+	help
+	  Allow user space to create what appear to be multiple instances
+	  of the network stack.
+
 config BLK_DEV_INITRD
 	bool "Initial RAM filesystem and RAM disk (initramfs/initrd) support"
 	depends on BROKEN || !FRV
net/Kconfig +0 -8
Index: linux-2.6.29-rc1/net/Kconfig
===================================================================
@@ -24,14 +24,6 @@ if NET
 
 menu "Networking options"
 
-config NET_NS
-	bool "Network namespace support"
-	default n
-	depends on EXPERIMENTAL && NAMESPACES
-	help
-	  Allow user space to create what appear to be multiple instances
-	  of the network stack.
-
 config COMPAT_NET_DEV_OPS
        def_bool y
Acked-by Serge Hallyn on v1 1/1
#1 lore raw
Quoted 4 lines · Matt Helsley

Make NET_NS available underneath the generic Namespaces config option since all of the other namespace options are there.

Signed-off-by Matt Helsley <[email protected]>

It would definately be nice to have all the namespace options in one place.

Acked-by Serge Hallyn <[email protected]>
Quoted 49 lines
---
 init/Kconfig |    8 ++++++++
 net/Kconfig  |    8 --------
 2 files changed, 8 insertions(+), 8 deletions(-)

Index: linux-2.6.29-rc1/init/Kconfig
===================================================================

init/Kconfig +8 -0
@@ -541,6 +541,14 @@ config PID_NS
 	  Unless you want to work with an experimental feature
 	  say N here.
 
+config NET_NS
+	bool "Network namespace"
+	default n
+	depends on NAMESPACES && EXPERIMENTAL && NET
+	help
+	  Allow user space to create what appear to be multiple instances
+	  of the network stack.
+
 config BLK_DEV_INITRD
 	bool "Initial RAM filesystem and RAM disk (initramfs/initrd) support"
 	depends on BROKEN || !FRV

Index: linux-2.6.29-rc1/net/Kconfig
===================================================================

net/Kconfig +0 -9
@@ -24,14 +24,6 @@ if NET
 
 menu "Networking options"
 
-config NET_NS
-	bool "Network namespace support"
-	default n
-	depends on EXPERIMENTAL && NAMESPACES
-	help
-	  Allow user space to create what appear to be multiple instances
-	  of the network stack.
-
 config COMPAT_NET_DEV_OPS
        def_bool y
 
 
 
--

To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

maintainer
#2 lore raw

From: "Serge E. Hallyn" <[email protected]>
Date: Mon, 26 Jan 2009 11:58:45 -0600

Quoted 10 lines · Matt Helsley
Quoted 4 lines

Make NET_NS available underneath the generic Namespaces config option since all of the other namespace options are there.

Signed-off-by Matt Helsley <[email protected]>

It would definately be nice to have all the namespace options in one place.

Acked-by Serge Hallyn <[email protected]>

Sounds good to me too, applied, thanks everyone.