On Fri, 6 Jul 2007, Stefan Richter wrote:
> Robert P. J. Day wrote:
> > --- a/arch/i386/kernel/io_apic.c
> > +++ b/arch/i386/kernel/io_apic.c
> > @@ -353,7 +353,7 @@ static void set_ioapic_affinity_irq(unsigned int irq,
> > cpumask_t cpumask)
> > # include <linux/slab.h> /* kmalloc() */
> > # include <linux/timer.h> /* time_after() */
> >
> > -#ifdef CONFIG_BALANCED_IRQ_DEBUG
> > +#if 0 /* debug IRQ balancing */
> > # define TDprintk(x...) do { printk("<%ld:%s:%d>: ", jiffies, __FILE__,
> > __LINE__); printk(x); } while (0)
> > # define Dprintk(x...) do { TDprintk(x); } while (0)
> > # else
>
> Regarding the Subject: Perhaps it's not of type "dead (K)config
> variable"in the strict sense but rather of the type "local macro
> whose name was unbefittingly taken from CONFIG_ namespace".
>
> BTW, when I suggested the "#if 0" to you, I forgot that some
> developers might be interested in compiling their kernel with
> -DCONFIG_BALANCED_IRQ_DEBUG injected via the commandline. But we'll
> hear from them if that's the case.
>
> On the other hand, these debug macros seem to be very old. I'll
> have a closer look with qgit/git-blame later today. Maybe it's time
> to remove them now.
ok, why don't i leave all that in your capable hands? typically, when
i describe a CONFIG_ prefixed variable as "dead", it's because it's
not being set *anywhere* in the tree -- not in a Kconfig file or a
header file or a source file or a Makefile.
so i'm not just checking for its existence in a Kconfig file. i
learned that lesson. :-)
rday
p.s. and i've bitched and moaned about this before, but anyone who
deliberately names their debugging variables with a "CONFIG_" prefix
*deserves* to have their builds break. :-P
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
http://fsdev.net/wiki/index.php?title=Main_Page
========================================================================
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
