| 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, 6 Aug 2010 21:49:51 -0700 (PDT) From: david@...g.hm To: Sam Ravnborg <sam@...nborg.org> cc: linux-kernel <linux-kernel@...r.kernel.org> Subject: Re: KCONFIG savedefconfig On Sat, 7 Aug 2010, Sam Ravnborg wrote: > On Fri, Aug 06, 2010 at 08:25:43PM -0700, david@...g.hm wrote: >> when savedefconfig decides what to write out, what does it do for things >> that are not at the default, but were set to not be default as part of >> dependancy resolution? > > The short version: > Any symbol that does not have default value are written to > the defconfig file. > > Using the defconfig file as input or using the full config file > as input shall result in the same configuration. > If not you found a bug we need to fix. Ok, so I take this to mean that if selecting one symbol forces selection of another, then both symbols will be written to the defconfig file, even though only the first would be needed to recreate the full file. this is a wonderful step forward, I'm just trying to understand the nuances of it. David Lang > Arve found one bug I have to look into - pending feedback. > And I have found one bug related to tristate choice values. > > So a bit work is needed to make it ready :-( > But it works for most of the defconfig we have today. -- 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