From: Josh Boyer <jwboyer@gmail.com>
To: Bernhard Walle <bwalle@suse.de>
Cc: linuxppc-dev@ozlabs.org, kexec@lists.infradead.org,
linux-kernel@vger.kernel.org, vgoyal@redhat.com
Subject: Re: [PATCH] Remove experimental status of kdump on PPC64
Date: Thu, 26 Jun 2008 11:28:52 -0400 [thread overview]
Message-ID: <1214494132.2791.0.camel@weaponx> (raw)
In-Reply-To: <1214485035-26041-1-git-send-email-bwalle@suse.de>
On Thu, 2008-06-26 at 14:57 +0200, Bernhard Walle wrote:
> This patch removes the experimental status of kdump on IA64. kdump is on IA64
> now since more than one year and it has proven to be stable.
I think you mean PPC64?
josh
> For i386/x86_64, a similar patch has been accepted by Ingo Molnar and Vivek
> Goyal.
>
>
> Signed-off-by: Bernhard Walle <bwalle@suse.de>
> ---
> arch/powerpc/Kconfig | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/powerpc/Kconfig b/arch/powerpc/Kconfig
> index 3934e26..2a116b9 100644
> --- a/arch/powerpc/Kconfig
> +++ b/arch/powerpc/Kconfig
> @@ -308,8 +308,8 @@ config KEXEC
> strongly in flux, so no good recommendation can be made.
>
> config CRASH_DUMP
> - bool "Build a kdump crash kernel (EXPERIMENTAL)"
> - depends on PPC_MULTIPLATFORM && PPC64 && EXPERIMENTAL
> + bool "Build a kdump crash kernel"
> + depends on PPC_MULTIPLATFORM && PPC64
> help
> Build a kernel suitable for use as a kdump capture kernel.
> The kernel will be linked at a different address than normal, and
next prev parent reply other threads:[~2008-06-26 15:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-26 12:57 [PATCH] Remove experimental status of kdump on PPC64 Bernhard Walle
2008-06-26 15:28 ` Josh Boyer [this message]
2008-06-26 17:02 ` Bernhard Walle
2008-06-26 17:02 ` Bernhard Walle
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=1214494132.2791.0.camel@weaponx \
--to=jwboyer@gmail.com \
--cc=bwalle@suse.de \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=vgoyal@redhat.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;
as well as URLs for NNTP newsgroup(s).