| 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 Jun 2008 08:39:21 +0200 From: Sam Ravnborg <sam@...nborg.org> To: Rob Landley <rob@...dley.net> Cc: Adrian Bunk <bunk@...nel.org>, Tim Bird <tim.bird@...sony.com>, linux-tiny <Linux-tiny@...enic.com>, linux-embedded <linux-embedded@...r.kernel.org>, linux kernel <linux-kernel@...r.kernel.org> Subject: Re: mainlining min-configs... > > > > When I get my kconfig patchset polished you will be able to do: > > > > make K=my_mini_config allnoconfig > > So you're renaming KCONFIG_ALLNOCONFIG then? Somehow yes. The K= notation I hope will see more use. Only very few people know the KCONFIG_ALL*CONFIG= trick. > > > Thus selecting 'no' for all new symbols in an automated fashion. > > I know that in a few cases 'no' is the wrong answer but in the > > 99% of the cases 'no' is perfectly valid. > > For a "make miniconfig", warnings should be errors. (Attempts to set unknown > symbols are an error with a miniconfig, the operation should exit with a > nonzero error code.) Also, all the stuff allnoconfig puts to stdout > shouldn't be there for miniconfig, only the stuff it writes to stderr right > now should show up. My reference was to a minimal config of a system - not to a miniconfig as your patcset produces. Just to make it clear. The patchset I refer will also reduce the nosie generated during make *config. Sam -- 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