public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Ben Collins <bcollins@ubuntu.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/6] i386/x86_64: Allow disabling the putstr's from compressed boot wrapper (fixed)
Date: Thu, 24 May 2007 13:44:33 -0700	[thread overview]
Message-ID: <20070524134433.731ef20f.akpm@linux-foundation.org> (raw)
In-Reply-To: <b31c080.git.bcollins@ubuntu.com>

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

> Updated to include proper spacing for putstr() macro.
> 
> Signed-off-by: Ben Collins <bcollins@ubuntu.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?

  parent reply	other threads:[~2007-05-24 20:44 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-23 21:59 [PATCH 0/6] Patch sync from Ubuntu tree Ben Collins
2007-05-23 21:59 ` [PATCH 1/6] i386/x86_64: Allow disabling the putstr's from compressed boot wrapper Ben Collins
2007-05-24  3:15   ` Randy Dunlap
2007-05-24 20:44   ` Andrew Morton [this message]
2007-05-25 11:33   ` Andi Kleen
2007-05-25 12:52     ` Ben Collins
2007-05-25 19:45       ` H. Peter Anvin
2007-05-25 23:23         ` Jesse Barnes
2007-05-25 23:28           ` H. Peter Anvin
2007-05-25 23:38             ` Jesse Barnes
2007-05-25 23:43               ` H. Peter Anvin
2007-05-25 23:50                 ` Jesse Barnes
2007-05-25 23:50             ` Ben Collins
2007-05-25 23:52               ` H. Peter Anvin
2007-05-23 22:18 ` [PATCH 2/6] PM: Do not require dev spew to get PM_DEBUG Ben Collins
2007-05-23 22:21 ` [PATCH 3/6] HCIUSB: Initialize the Broadcom USB Bluetooth device in Dell laptops Ben Collins
2007-05-24 17:02   ` Marcel Holtmann
2007-05-24 17:33     ` Ben Collins
2007-05-23 22:23 ` [PATCH 4/6] RTC: Ratelimit "lost interrupts" message Ben Collins
2007-05-24 20:48   ` Andrew Morton
2007-05-24 20:56     ` Ben Collins
2007-05-24 21:09       ` Andrew Morton
2007-05-24 21:15         ` Roland Dreier
2007-05-24 21:16         ` Zachary Amsden
2007-05-23 22:30 ` [PATCH 5/6] SUNHME: Workaround ancient hang on U1's Ben Collins
2007-05-24  0:17   ` David Miller
2007-05-24  1:59     ` Ben Collins
2007-05-24 12:30   ` Daniel Drake
2007-05-23 22:39 ` [PATCH 6/6] UNUSUAL_DEV: Sync up some reported devices from Ubuntu Ben Collins
2007-05-24  3:59   ` Phil Dibowitz
2007-05-24  4:09     ` Ben Collins
2007-05-30 21:50   ` Dave Jones
2007-05-30 22:25     ` Phil Dibowitz

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=20070524134433.731ef20f.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=bcollins@ubuntu.com \
    --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