linux-kernel - Re: [RFC] kconfig: introduce alldefconfig + savedefconfig

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20100725222023.GA9835@merkur.ravnborg.org>
Date:	Mon, 26 Jul 2010 00:20:23 +0200
From:	Sam Ravnborg <sam@...nborg.org>
To:	lkml <linux-kernel@...r.kernel.org>,
	linux-kbuild <linux-kbuild@...r.kernel.org>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	Roman Zippel <zippel@...ux-m68k.org>,
	Michal Marek <mmarek@...e.cz>,
	Uwe Kleine-Koig <u.kleine-koenig@...gutronix.de>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [RFC] kconfig: introduce alldefconfig + savedefconfig

> in kconfig is preferable.
> 
> This patch set introduce "alldefconfig".
> alldefconfig create a configuration with all values set
> to default values.
> This can be usefull when we check if we do have a sane
> set of default values. Rhe config can be inspected
> using menuconfig.
> 
> The patches also introduce "savedefconfig" which
> reads the current configuration and save it
> as a minimal configuration.

A funny detail that I used in my testing.

If we create a config based solely on default values like this:

   make alldefconfig

then when we later save the minimal config like this:

    make savedefconfig

then the resulting defconfig file is empty.
This is as expected because all symbols has default values
so there is no need to save the value of any symbol.

	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/