linux-kernel - Re: [PATCH] Remove experimental status of kdump on PPC64

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1214494132.2791.0.camel@weaponx>
Date:	Thu, 26 Jun 2008 11:28:52 -0400
From:	Josh Boyer <jwboyer@...il.com>
To:	Bernhard Walle <bwalle@...e.de>
Cc:	linuxppc-dev@...abs.org, kexec@...ts.infradead.org,
	linux-kernel@...r.kernel.org, vgoyal@...hat.com
Subject: Re: [PATCH] Remove experimental status of kdump on PPC64

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@...e.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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/