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: Fri, 20 Jul 2007 18:48:43 +0200 From: Stefan Richter <stefanr@...6.in-berlin.de> To: Chris Snook <csnook@...hat.com> CC: Satyam Sharma <satyam.sharma@...il.com>, "clameter@....com" <clameter@....com>, linux-kernel@...r.kernel.org, linux-mm@...ck.org, akpm@...ux-foundation.org Subject: Re: [RFC 1/4] CONFIG_STABLE: Define it Chris Snook wrote: > There are many different ways you can use it. If I'm writing a configurable > feature, I could make it depend on !CONFIG_STABLE, or I could ifdef my code out > if CONFIG_STABLE is set, unless a more granular option is also set. The > maintainer of the code that uses the config option has a lot of flexibility, In other words, nobody will ever know what this config option really does. > at least until we start enforcing standards. -- Stefan Richter -=====-=-=== -=== =-=-- http://arcgraph.de/sr/ - 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