From: Pavel Emelyanov <xemul@openvz.org>
To: Andrew Morton <akpm@osdl.org>
Cc: Cedric Le Goater <clg@fr.ibm.com>,
Serge Hallyn <serue@us.ibm.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Linux Containers <containers@lists.osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [PATCH 6/6] Mark NET_NS with "depends on NAMESPACES"
Date: Wed, 14 Nov 2007 14:41:14 +0300 [thread overview]
Message-ID: <473ADEDA.8060706@openvz.org> (raw)
In-Reply-To: <473ADB5B.50902@openvz.org>
There's already an option controlling the net namespaces
cloning code, so make it work the same way as all the
other namespaces' options.
Should I wait till the option itself gets to mainline and
resend this patch to David?
Signed-off-by: Pavel Emelyanov <xemul@openvz.org>
---
diff --git a/net/Kconfig b/net/Kconfig
index ab4e6da..d61a025 100644
--- a/net/Kconfig
+++ b/net/Kconfig
@@ -30,7 +30,7 @@ menu "Networking options"
config NET_NS
bool "Network namespace support"
default n
- depends on EXPERIMENTAL && !SYSFS
+ depends on EXPERIMENTAL && !SYSFS && NAMESPACES
help
Allow user space to create what appear to be multiple instances
of the network stack.
next prev parent reply other threads:[~2007-11-14 11:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-14 11:26 [PATCH 0/6] A config option to compile out some namespaces code (v4) Pavel Emelyanov
2007-11-14 11:28 ` [PATCH 1/6] Add the NAMESPACES config option Pavel Emelyanov
2007-11-14 11:30 ` [PATCH 2/6] Move the UTS namespace under UTS_NS option Pavel Emelyanov
2007-11-14 11:32 ` [PATCH 3/6] Move the IPC namespace under IPC_NS option Pavel Emelyanov
2007-11-14 11:36 ` [PATCH 4/6] Cleanup the code managed with the USER_NS option Pavel Emelyanov
2007-11-14 11:39 ` [PATCH 5/6] Cleanup the code managed with PID_NS option Pavel Emelyanov
2007-11-14 11:41 ` Pavel Emelyanov [this message]
2007-11-14 14:58 ` [PATCH 0/6] A config option to compile out some namespaces code (v4) Serge E. Hallyn
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=473ADEDA.8060706@openvz.org \
--to=xemul@openvz.org \
--cc=akpm@osdl.org \
--cc=clg@fr.ibm.com \
--cc=containers@lists.osdl.org \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=serue@us.ibm.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox