From: Robert Love <rml@tech9.net>
To: "David S. Miller" <davem@redhat.com>
Cc: vda@port.imtp.ilyichevsk.odessa.ua, 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: 11 Mar 2002 14:43:03 -0500 [thread overview]
Message-ID: <1015875785.928.45.camel@phantasy> (raw)
In-Reply-To: <20020311.060324.69703263.davem@redhat.com>
In-Reply-To: <200203111359.g2BDx1q05409@Port.imtp.ilyichevsk.odessa.ua> <20020311.060324.69703263.davem@redhat.com>
On Mon, 2002-03-11 at 09:03, David S. Miller wrote:
> Maybe it is even better idea to change default kernel printk
> logging level which is used when no KERN_* is specified, eh?
Only if we really consider the printks in question "whatever the default
is." The default has changed before and may change again (as you are
suggesting). I have no problem changing the default - I just think if
Denis suggests a printk should be classified as "informative" and we
agree, let's change it. Although I don't think it would fly with Linus,
any printk we can solidly classify we should, imo.
This doesn't preclude changing the default, as you suggest, especially
if its clearly too high. But I don't see why we shouldn't be explicit
where possible. No?
Robert Love
prev parent reply other threads:[~2002-03-11 19:43 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
2002-03-11 18:56 ` Denis Vlasenko
2002-03-11 19:43 ` Robert Love [this message]
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=1015875785.928.45.camel@phantasy \
--to=rml@tech9.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davem@redhat.com \
--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