[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <19f34abd0710052310r2043f69ew70fe8b5f9ef0493c@mail.gmail.com>
Date: Sat, 6 Oct 2007 08:10:26 +0200
From: "Vegard Nossum" <vegard.nossum@...il.com>
To: "Rob Landley" <rob@...dley.net>
Cc: "Miguel Ojeda" <maxextreme@...il.com>,
"Randy Dunlap" <randy.dunlap@...cle.com>,
LKML <linux-kernel@...r.kernel.org>,
"Kyle Moffett" <mrmacman_g4@....com>,
"Michael Holzheu" <holzheu@...ux.vnet.ibm.com>,
"Joe Perches" <joe@...ches.com>,
"Dick Streefland" <dick.streefland@...ium.nl>,
"Geert Uytterhoeven" <Geert.Uytterhoeven@...ycom.com>,
"Jesse Barnes" <jesse.barnes@...el.com>,
"Arnd Bergmann" <arnd@...db.de>,
"Jan Engelhardt" <jengelh@...putergmbh.de>,
"Emil Medve" <Emilian.Medve@...escale.com>,
"Stephen Hemminger" <shemminger@...ux-foundation.org>,
"linux@...izon.com" <linux@...izon.com>
Subject: Re: [RFC][PATCH] New message-logging API (kprint)
On 10/5/07, Rob Landley <rob@...dley.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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists