From: ebiederm@xmission.com (Eric W. Biederman)
To: Andrew Morton <akpm@osdl.org>
Cc: <linux-kernel@vger.kernel.org>, <fastboot@osdl.org>,
Andi Kleen <ak@suse.de>
Subject: [PATCH] x86_64 kexec: Remove experimental mark of kexec
Date: Wed, 06 Sep 2006 10:55:49 -0600 [thread overview]
Message-ID: <m1k64hvsru.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <m1veo1vtev.fsf@ebiederm.dsl.xmission.com> (Eric W. Biederman's message of "Wed, 06 Sep 2006 10:42:00 -0600")
kexec has been marked experimental for a year now and all
of the serious problems have been worked through. So it
is time (if not past time) to remove the experimental mark.
Signed-off-by: Eric W. Biederman <ebiederm@xmission.com>
---
This time with a Signed-off-by line.
arch/x86_64/Kconfig | 3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/arch/x86_64/Kconfig b/arch/x86_64/Kconfig
index 756fa38..1adba0f 100644
--- a/arch/x86_64/Kconfig
+++ b/arch/x86_64/Kconfig
@@ -481,8 +481,7 @@ config X86_MCE_AMD
the DRAM Error Threshold.
config KEXEC
- bool "kexec system call (EXPERIMENTAL)"
- depends on EXPERIMENTAL
+ bool "kexec system call"
help
kexec is a system call that implements the ability to shutdown your
current kernel, and to start another kernel. It is like a reboot
--
1.4.2.rc3.g7e18e-dirty
next prev parent reply other threads:[~2006-09-06 16:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-06 16:42 [PATCH] x86_64 kexec: Remove experimental mark of kexec Eric W. Biederman
2006-09-06 16:55 ` Eric W. Biederman [this message]
2006-09-06 19:22 ` Andi Kleen
2006-09-06 20:15 ` Eric W. Biederman
2006-09-07 6:20 ` Piet Delaney
2006-09-07 6:55 ` Eric W. Biederman
2006-09-08 1:54 ` Piet Delaney
2006-09-07 5:47 ` Piet Delaney
2006-09-07 6:03 ` Eric W. Biederman
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=m1k64hvsru.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=fastboot@osdl.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox