From: "Vegard Nossum" <vegard.nossum@gmail.com>
To: "Rob Landley" <rob@landley.net>
Cc: "Miguel Ojeda" <maxextreme@gmail.com>,
"Randy Dunlap" <randy.dunlap@oracle.com>,
LKML <linux-kernel@vger.kernel.org>,
"Kyle Moffett" <mrmacman_g4@mac.com>,
"Michael Holzheu" <holzheu@linux.vnet.ibm.com>,
"Joe Perches" <joe@perches.com>,
"Dick Streefland" <dick.streefland@altium.nl>,
"Geert Uytterhoeven" <Geert.Uytterhoeven@sonycom.com>,
"Jesse Barnes" <jesse.barnes@intel.com>,
"Arnd Bergmann" <arnd@arndb.de>,
"Jan Engelhardt" <jengelh@computergmbh.de>,
"Emil Medve" <Emilian.Medve@freescale.com>,
"Stephen Hemminger" <shemminger@linux-foundation.org>,
"linux@horizon.com" <linux@horizon.com>
Subject: Re: [RFC][PATCH] New message-logging API (kprint)
Date: Sat, 6 Oct 2007 08:10:26 +0200 [thread overview]
Message-ID: <19f34abd0710052310r2043f69ew70fe8b5f9ef0493c@mail.gmail.com> (raw)
In-Reply-To: <200710051126.50816.rob@landley.net>
On 10/5/07, Rob Landley <rob@landley.net> wrote:
> The original idea (selectively compile out printk() instances based on log
> level to conserve space) is explicitly not addressed by this patch, and in
> fact this patch might actually make it harder to implement (by complicating
> the code).
This is wrong. The patch provides log-level-based filtering at compile
time, effectively making the kernel smaller.
> *shrug* That doesn't mean my objections are important to anyone else, just
> that I don't personally see any reason to be enthusiastic about this patch.
I agree; you are right about the other things, Maybe I can try to fit
some of these things into printk itself (thanks for the tip, Alan),
and we'll see how far we can get.
Thanks.
Vegard
next prev parent reply other threads:[~2007-10-06 6:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-04 20:04 Vegard Nossum
2007-10-04 20:17 ` Randy Dunlap
2007-10-05 1:59 ` Rob Landley
2007-10-05 7:01 ` Miguel Ojeda
2007-10-05 16:26 ` Rob Landley
2007-10-05 23:01 ` Miguel Ojeda
2007-10-06 0:34 ` Stephen Hemminger
2007-10-07 10:20 ` Miguel Ojeda
2007-10-07 21:56 ` Rob Landley
2007-10-07 22:32 ` Randy Dunlap
2007-10-06 6:10 ` Vegard Nossum [this message]
2007-10-07 21:50 ` Rob Landley
2007-10-08 15:25 ` Stephen Hemminger
2007-10-08 15:33 ` Vegard Nossum
2007-10-08 15:42 ` Stephen Hemminger
2007-10-05 13:13 ` Vegard Nossum
2007-10-05 16:05 ` Rob Landley
2007-10-05 17:01 ` Alan Cox
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=19f34abd0710052310r2043f69ew70fe8b5f9ef0493c@mail.gmail.com \
--to=vegard.nossum@gmail.com \
--cc=Emilian.Medve@freescale.com \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=arnd@arndb.de \
--cc=dick.streefland@altium.nl \
--cc=holzheu@linux.vnet.ibm.com \
--cc=jengelh@computergmbh.de \
--cc=jesse.barnes@intel.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@horizon.com \
--cc=maxextreme@gmail.com \
--cc=mrmacman_g4@mac.com \
--cc=randy.dunlap@oracle.com \
--cc=rob@landley.net \
--cc=shemminger@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®