Hi, On Sat, 23 Jun 2007, Satyam Sharma wrote: > 1. Kconfig symbols will always have code associated with them. > That's the entire purpose of Kconfig, is it not? A possible counter example: CONFIG_SCSI. (RAID_ATTRS is currently a little misplaced). It's optional for any config symbol to have any code attached to it, menuconfig doesn't change anything. > 2. "menuconfig" symbols, otoh, were _invented_ for another reason > entirely: presentation and user interface i.e. so that users are able > to disable entire menus (and all the options contained therein) > without having to enter into the menu first, and without having to > disable all options individually (which was the situation that existed > before the introduction of these menuconfig objects). Since I'm the one who _invented_ it, I can tell you you're wrong. :) This functionality isn't limited to menuconfig symbols. The menu option simply changes how the child symbols can be displayed. bye, Roman - 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/
- Follow-Ups:
- References:
- Kconfig troubles when using menuconfig - Was: [patch]Re: [linux-usb-devel] linux-2.6.22-rc5-gf1518a0 build #300 failed in zc0301_core.c
- From: Mauro Carvalho Chehab <[email protected]>
- Re: Kconfig troubles when using menuconfig - Was: [patch]Re: [linux-usb-devel] linux-2.6.22-rc5-gf1518a0 build #300 failed in zc0301_core.c
- From: Trent Piepho <[email protected]>
- Re: Kconfig troubles when using menuconfig - Was: [patch]Re: [linux-usb-devel] linux-2.6.22-rc5-gf1518a0 build #300 failed in zc0301_core.c
- From: "Satyam Sharma" <[email protected]>
- Re: Kconfig troubles when using menuconfig - Was: [patch]Re: [linux-usb-devel] linux-2.6.22-rc5-gf1518a0 build #300 failed in zc0301_core.c
- From: Roman Zippel <[email protected]>
- Re: Kconfig troubles when using menuconfig - Was: [patch]Re: [linux-usb-devel] linux-2.6.22-rc5-gf1518a0 build #300 failed in zc0301_core.c
- From: "Satyam Sharma" <[email protected]>
- Re: Kconfig troubles when using menuconfig - Was: [patch]Re: [linux-usb-devel] linux-2.6.22-rc5-gf1518a0 build #300 failed in zc0301_core.c
- From: Roman Zippel <[email protected]>
- Re: Kconfig troubles when using menuconfig - Was: [patch]Re: [linux-usb-devel] linux-2.6.22-rc5-gf1518a0 build #300 failed in zc0301_core.c
- From: "Satyam Sharma" <[email protected]>
- Kconfig troubles when using menuconfig - Was: [patch]Re: [linux-usb-devel] linux-2.6.22-rc5-gf1518a0 build #300 failed in zc0301_core.c
- Prev by Date: Re: how to tell linux (on x86) to ignore 1M or memory
- Next by Date: Re: [PATCH] x86-64: disable the GART before allocate aperture
- Previous by thread: Re: Kconfig troubles when using menuconfig - Was: [patch]Re: [linux-usb-devel] linux-2.6.22-rc5-gf1518a0 build #300 failed in zc0301_core.c
- Next by thread: Re: Kconfig troubles when using menuconfig - Was: [patch]Re: [linux-usb-devel] linux-2.6.22-rc5-gf1518a0 build #300 failed in zc0301_core.c
- Index(es):