From: Dave Hansen <dave-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
To: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Cc: Dave Hansen <dave-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
Subject: [PATCH 2/4] Move checkpoint closer to namespaces
Date: Fri, 05 Jun 2009 12:15:27 -0700 [thread overview]
Message-ID: <20090605191527.05B6C68E@kernel> (raw)
In-Reply-To: <20090605191525.C3F1C2F2@kernel>
These are pretty intimately related, so let's make them
closer to each other in Kconfig. This shoudl be pushed
up into the patch that creates CONFIG_CHECKPOINT in the
first place.
---
linux-2.6.git-dave/init/Kconfig | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff -puN init/Kconfig~move-cr-close-to-namespaces init/Kconfig
--- linux-2.6.git/init/Kconfig~move-cr-close-to-namespaces 2009-06-05 11:45:19.000000000 -0700
+++ linux-2.6.git-dave/init/Kconfig 2009-06-05 11:57:46.000000000 -0700
@@ -709,6 +709,8 @@ config NET_NS
Allow user space to create what appear to be multiple instances
of the network stack.
+source "checkpoint/Kconfig"
+
config BLK_DEV_INITRD
bool "Initial RAM filesystem and RAM disk (initramfs/initrd) support"
depends on BROKEN || !FRV
@@ -1042,8 +1044,6 @@ config SLOW_WORK
See Documentation/slow-work.txt.
-source "checkpoint/Kconfig"
-
endmenu # General setup
config HAVE_GENERIC_DMA_COHERENT
_
next prev parent reply other threads:[~2009-06-05 19:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-05 19:15 [PATCH 1/4] Namespaces submenu Dave Hansen
2009-06-05 19:15 ` Dave Hansen [this message]
2009-06-05 19:15 ` [PATCH 3/4] kill 'Enable' in c/r config option Dave Hansen
2009-06-05 19:15 ` [PATCH 4/4] Conditionally force on namespaces Dave Hansen
2009-06-05 19:35 ` Serge E. Hallyn
[not found] ` <20090605193538.GA22848-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-06-05 21:21 ` Nathan Lynch
2009-06-08 6:21 ` Oren Laadan
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=20090605191527.05B6C68E@kernel \
--to=dave-23vcf4htsmix0ybbhkvfkdbpr1lh4cv8@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox