From: Matt Helsley <matthltc@us.ibm.com>
To: netdev <netdev@vger.kernel.org>
Subject: [PATCH][RFC] Move config NET_NS to from net/Kconfig to init/Kconfig
Date: Fri, 23 Jan 2009 16:07:31 -0800 [thread overview]
Message-ID: <1232755651.8282.6.camel@localhost> (raw)
Make NET_NS available underneath the generic Namespaces config option since all of
the other namespace options are there.
Signed-off-by: Matt Helsley <matthltc@us.ibm.com>
---
init/Kconfig | 8 ++++++++
net/Kconfig | 8 --------
2 files changed, 8 insertions(+), 8 deletions(-)
Index: linux-2.6.29-rc1/init/Kconfig
===================================================================
--- linux-2.6.29-rc1.orig/init/Kconfig
+++ 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
Index: linux-2.6.29-rc1/net/Kconfig
===================================================================
--- linux-2.6.29-rc1.orig/net/Kconfig
+++ 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
next reply other threads:[~2009-01-24 0:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-24 0:07 Matt Helsley [this message]
2009-01-26 17:58 ` [PATCH][RFC] Move config NET_NS to from net/Kconfig to init/Kconfig Serge E. Hallyn
2009-01-26 20:26 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1232755651.8282.6.camel@localhost \
--to=matthltc@us.ibm.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.