lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 11 Apr 2007 07:42:38 +0300 From: Al Boldi <a1426z@...ab.com> To: Jan Engelhardt <jengelh@...ux01.gwdg.de> Cc: linux-kernel@...r.kernel.org Subject: Re: [PATCH 0/30] Use menuconfig objects Jan Engelhardt wrote: > On Apr 11 2007 01:12, Al Boldi wrote: > >Jan Engelhardt wrote: > >> the following patch series turns some menus into menuconfigs, so they > >> can be disabled whilst "walking" thorugh the parent menu > > > >Great, but instead of making it a simple on/off, make it tri-state that > > would default select all child-options appropriately. (see HW_RANDOM) > > I do not remember having touched the Random Number Generators or Character > Devices anywhere in this series. > > Don't worry, I have paid attention (or at least I hope so ;-) to > 'm'-able options, for example the SCSI, IEEE1394, or I2C stacks. > > But, for example you will see > [*] Old CD-ROM drivers (not SCSI, not IDE) > > which is because this entry in itself does not generate any object file. > > Generally, I just made the 'menuconfig' entry have the same state > (bool/tristate) as the original entry. If I have overseen that > somewhere, please let me know! Correct, no oversight here; but it may be more meaningful, if you could default select child-options based on the parent-state, like HW_RANDOM. Also, I don't think it's necessary to touch any of the "depends on"; keep them as is, as they don't hurt staying that way, and may actually be necessary under certain circumstances. (see EMBEDDED) Thanks! -- Al - 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