From: Steven Rostedt <rostedt@goodmis.org>
To: Matt Mackall <mpm@selenic.com>
Cc: Andrew Morton <akpm@osdl.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] clean up kernel messages
Date: Fri, 01 Apr 2005 16:18:42 -0500 [thread overview]
Message-ID: <1112390323.578.1.camel@localhost.localdomain> (raw)
In-Reply-To: <20050401204629.GJ15453@waste.org>
On Fri, 2005-04-01 at 12:46 -0800, Matt Mackall wrote:
> On Fri, Apr 01, 2005 at 12:26:41PM -0800, Andrew Morton wrote:
> > Matt Mackall <mpm@selenic.com> wrote:
> > >
> > > This patch tidies up those annoying kernel messages. A typical kernel
> > > boot now looks like this:
> > >
> > > Loading Linux... Uncompressing kernel...
> > > #
> > >
> > > See? Much nicer. This patch saves about 375k on my laptop config and
> > > nearly 100k on minimal configs.
> > >
> >
> > heh. Please take a look at
> > http://www.uwsg.iu.edu/hypermail/linux/kernel/0004.2/0709.html, see if
> > Graham did anything which you missed.
>
> He's got a bunch of stuff that's not strictly related in there and
> stuff I've already dealt with (vprintk and the like) and stuff that's
> still forthcoming (panic tweaks, etc.). I also leave in all the APIs
> like dmesg, they just no longer do anything.
Looking at your other patches, I'm assuming that this is just another
April 1st type of patch. Is it?
-- Steve
next prev parent reply other threads:[~2005-04-01 21:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-01 20:08 [PATCH] clean up kernel messages Matt Mackall
2005-04-01 20:26 ` Andrew Morton
2005-04-01 20:46 ` Matt Mackall
2005-04-01 21:18 ` Steven Rostedt [this message]
2005-04-01 21:26 ` Steven Rostedt
2005-04-01 22:08 ` Richard B. Johnson
2005-04-02 10:35 ` Denis Vlasenko
2005-04-01 21:32 ` Matt Mackall
2005-04-01 20:27 ` Jan-Benedict Glaw
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=1112390323.578.1.camel@localhost.localdomain \
--to=rostedt@goodmis.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
/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.