From: Denis Vlasenko <vda@ilport.com.ua>
To: linux-os@analogic.com, Steven Rostedt <rostedt@goodmis.org>
Cc: Matt Mackall <mpm@selenic.com>, Andrew Morton <akpm@osdl.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] clean up kernel messages
Date: Sat, 2 Apr 2005 13:35:07 +0300 [thread overview]
Message-ID: <200504021335.07611.vda@ilport.com.ua> (raw)
In-Reply-To: <Pine.LNX.4.61.0504011703400.30945@chaos.analogic.com>
On Saturday 02 April 2005 01:08, Richard B. Johnson wrote:
> >> Looking at your other patches, I'm assuming that this is just another
> >> April 1st type of patch. Is it?
> >
> > Arg! I'm too tired. I took another look at your other patches and they
> > look more legit now. On first glance, I thought you were just bluntly
> > removing BUGs and error messages to quiet things down. But after taking
> > another look, I see that they are more than that. I wouldn't of thought
> > about that on any other day.
> >
> > Sorry,
> >
> >
> > -- Steve
>
> Methinks he still is kidding. We have "quiet" as a parameter now
> to quiet things down on a boot. Now if he would just get rid
> of the annoying...
> >>>>> Loading Linux... Uncompressing kernel...
> He'd have something.
I suppose this is intended for embedded builds for devices with
no means whatsoever to send kernel log anywhere humanly visible.
--
vda
next prev parent reply other threads:[~2005-04-02 10:35 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
2005-04-01 21:26 ` Steven Rostedt
2005-04-01 22:08 ` Richard B. Johnson
2005-04-02 10:35 ` Denis Vlasenko [this message]
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=200504021335.07611.vda@ilport.com.ua \
--to=vda@ilport.com.ua \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.com \
--cc=mpm@selenic.com \
--cc=rostedt@goodmis.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.