From: "David S. Miller" <davem@redhat.com>
To: vda@port.imtp.ilyichevsk.odessa.ua
Cc: alan@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org,
marcelo@conectiva.com.br
Subject: Re: [PATCH] KERN_INFO 2.4.19-pre2 IP/TCP hash table size printks
Date: Mon, 11 Mar 2002 06:03:24 -0800 (PST) [thread overview]
Message-ID: <20020311.060324.69703263.davem@redhat.com> (raw)
In-Reply-To: <200203111359.g2BDx1q05409@Port.imtp.ilyichevsk.odessa.ua>
In-Reply-To: <200203111359.g2BDx1q05409@Port.imtp.ilyichevsk.odessa.ua>
From: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>
Date: Mon, 11 Mar 2002 15:58:15 -0200
Primary purpose of this patch is to make KERN_WARNING and
KERN_INFO log levels closer to their original meaning.
Today they are quite far from what was intended.
Just look what kernel writes at the WARNING level
each time you boot your box!
Maybe it is even better idea to change default kernel printk
logging level which is used when no KERN_* is specified, eh?
next prev parent reply other threads:[~2002-03-11 14:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-11 17:58 [PATCH] KERN_INFO 2.4.19-pre2 IP/TCP hash table size printks Denis Vlasenko
2002-03-11 14:03 ` David S. Miller [this message]
2002-03-11 18:56 ` Denis Vlasenko
2002-03-11 19:43 ` Robert Love
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=20020311.060324.69703263.davem@redhat.com \
--to=davem@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
/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