All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: Andrew Morton <akpm@osdl.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [patch] x86_64: don't use early_printk() during memory init
Date: Sat, 25 Feb 2006 05:26:05 +0100	[thread overview]
Message-ID: <200602250526.06389.ak@suse.de> (raw)
In-Reply-To: <200602242049_MC3-1-B938-400B@compuserve.com>

On Saturday 25 February 2006 02:45, Chuck Ebbert wrote:
> printk is working by the time this memory init message prints.
> As it stands, output jumps to the top of the screen and prints
> this message, then back to normal boot messages, overwriting
> a line at the top.

Using of early_printk here was intentional because it needs
much less infrastructure than printk and is pretty good proof
that the kernel at least started.

So please don't apply the patch.

-Andi

  reply	other threads:[~2006-02-25  4:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-25  1:45 [patch] x86_64: don't use early_printk() during memory init Chuck Ebbert
2006-02-25  4:26 ` Andi Kleen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-02-25  6:22 Chuck Ebbert

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=200602250526.06389.ak@suse.de \
    --to=ak@suse.de \
    --cc=76306.1226@compuserve.com \
    --cc=akpm@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.