Randy> Sure, autoconf.h is included, but I think his point is that
Randy> CONFIG_WATCHDOG_NOWAYOUT may not be defined there at all,
Randy> as in my 2.6.18-rc4 autoconf.h file, since my .config file
Randy> says: # CONFIG_WATCHDOG_NOWAYOUT is not set
Huh? How would including <linux/config.h> help with that? And why
would you want CONFIG_WATCHDOG_NOWAYOUT to be defined if
WATCHDOG_NOWAYOUT is not set in your configuration? That would
utterly break code that does something like
#ifdef CONFIG_WATCHDOG_NOWAYOUT
- R.
-
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/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
