[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200709281130.26124.rob@landley.net>
Date: Fri, 28 Sep 2007 11:30:25 -0500
From: Rob Landley <rob@...dley.net>
To: "Vegard Nossum" <vegard.nossum@...il.com>
Cc: 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] New kernel-message logging API (take 2)
On Friday 28 September 2007 7:11:03 am Vegard Nossum wrote:
> wrong. We can, however, use KBUILD_MODNAME as a default value for
> KPRINT_DRIVER, like:
> static const char *KPRINT_DRIVER = KBUILD_MODNAME;
> which would pre-process to something like:
> static const char *KPRINT_DRIVER = "bcm43xx";
Which has been known to result in the string getting written out to the .o
file even if it's never used, just in case something tries to take its
address. This is not the same as a #define.
> This value can still be overridden using #define KPRINT_DRIVER "new
> name".
Not with -D on the command line though. Your #define would have to come after
the declaration or else the declaration turns into 'char *"fred" = "george";'
and you have a syntax error. Again, not synonymous with a #define...
Rob
--
"One of my most productive days was throwing away 1000 lines of code."
- Ken Thompson.
-
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