From: Joe Perches <joe@perches.com>
To: Rasmus Andersen <rasmus@jaquet.dk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] CONFIG_TINY
Date: 23 Oct 2002 13:11:58 -0400 [thread overview]
Message-ID: <1035393119.10067.13.camel@localhost.localdomain> (raw)
In-Reply-To: <20021023215117.A29134@jaquet.dk>
On Wed, 2002-10-23 at 15:51, Rasmus Andersen wrote:
> o reduce usage of prinkt in kernel by #defining iprintk for
> INFO messages etc and let the desired (minimum) logging
> level be decided at compile time.
kernel.h already has #defines for pr_debug and pr_info.
perhaps all 8 current KERN_xxx's could be pr_#define'd
and the printks converted during 2.7+
I think this should be done together with Larry Kessler's
kernel logging proposal.
next prev parent reply other threads:[~2002-10-23 20:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-23 19:51 Rasmus Andersen
2002-10-23 17:11 ` Joe Perches [this message]
2002-10-24 20:40 ` Rasmus Andersen
2002-10-23 20:08 ` Christoph Hellwig
2002-10-23 20:39 ` Rasmus Andersen
2002-10-24 3:01 ` Elladan
2002-10-25 5:19 ` Untested patch 1/2 - add ugly printk macros to kernel (was Re: [RFC] CONFIG_TINY) Elladan
2002-10-25 5:20 ` Untested patch 2/2 - Fix some kernel sources for macro printk " Elladan
2002-10-24 20:38 ` [RFC] CONFIG_TINY Rasmus Andersen
2002-10-25 21:45 ` Daniel Phillips
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=1035393119.10067.13.camel@localhost.localdomain \
--to=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rasmus@jaquet.dk \
/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
Powered by JetHome