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>,
Linus Torvalds <torvalds@osdl.org>
Subject: Re: [patch] x86: clean up early_printk output
Date: Sat, 25 Feb 2006 05:29:10 +0100 [thread overview]
Message-ID: <200602250529.11099.ak@suse.de> (raw)
In-Reply-To: <200602241909_MC3-1-B93E-25B@compuserve.com>
On Saturday 25 February 2006 01:07, Chuck Ebbert wrote:
> early_printk() starts output on the second screen line and doesn't
> clear the rest of the line when it hits a newline char. When there
> is already a BIOS message there, it becomes hard to read. Change
> this so it starts on the first line and clears to EOL upon hitting
> newline.
early_printk is designed to do absolutely minimal work to get the
message out. Your patch adds too much potential disturbance
imho.
-Andi
next prev parent reply other threads:[~2006-02-25 4:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-25 0:07 [patch] x86: clean up early_printk output Chuck Ebbert
2006-02-25 2:07 ` Andrew Morton
2006-02-25 4:29 ` 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=200602250529.11099.ak@suse.de \
--to=ak@suse.de \
--cc=76306.1226@compuserve.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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