linux-kernel - Re: [PATCH 1/6] i386/x86_64: Allow disabling the putstr's from compressed boot wrapper (fixed)

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]

Date:	Thu, 24 May 2007 13:44:33 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Ben Collins <bcollins@...ntu.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/6] i386/x86_64: Allow disabling the putstr's from
 compressed boot wrapper (fixed)

On Wed, 23 May 2007 17:59:10 -0400
Ben Collins <bcollins@...ntu.com> wrote:

> Updated to include proper spacing for putstr() macro.
> 
> Signed-off-by: Ben Collins <bcollins@...ntu.com>
> ---
>  arch/i386/Kconfig.debug            |    6 ++++++
>  arch/i386/boot/compressed/misc.c   |    8 +++++---
>  arch/x86_64/Kconfig.debug          |    6 ++++++
>  arch/x86_64/boot/compressed/misc.c |    8 +++++---
>  4 files changed, 22 insertions(+), 6 deletions(-)
> 
> diff --git a/arch/i386/Kconfig.debug b/arch/i386/Kconfig.debug
> --- a/arch/i386/Kconfig.debug
> +++ b/arch/i386/Kconfig.debug
> @@ -19,6 +19,12 @@ config EARLY_PRINTK
>  	  with klogd/syslogd or the X server. You should normally N here,
>  	  unless you want to debug such a crash.
>  
> +config WRAPPER_PRINT
> +	bool "Boot wrapper print" if EMBEDDED
> +	default y
> +	help
> +	  Enable informational output from the bootwrapper (bzImage and zImage).
> +

What is the reason for making this change to the kernel?
-
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/