linux-kernel - Re: ARM defconfig files

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: <1275601717.23384.168.camel@c-dwalke-linux.qualcomm.com>
Date:	Thu, 03 Jun 2010 14:48:37 -0700
From:	Daniel Walker <dwalker@...eaurora.org>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Russell King <rmk@....linux.org.uk>,
	Kevin Hilman <khilman@...prootsystems.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-arm-msm@...r.kernel.org
Subject: Re: ARM defconfig files

On Thu, 2010-06-03 at 13:31 -0700, Linus Torvalds wrote:
> and now you'd be able to basically generate a OMAP3EVM .config file by 
> just running "allnoconfig" on that Kconfig.omap3_evm file. But it would 
> only have to select the parts that are specific for the EVM platform, 
> because the generic OMAP3 support would be picked by the Kconfig.omap3 
> file, which in turn would not have to worry about the generic ARM parts 
> etc.
> 
> See?

We could just alias commands so when the user runs

"make ARCH=arm omap3_evm_defconfig"

it would just do whatever this command does ,

"KBUILD_KCONFIG=arch/arm/configs/Kconfig.omap3_evm make allnoconfig"

but those Kconfigs wouldn't be in "make menuconfig" it would just exist
to generate the defconfigs, or the .config .. So Kconfig.omap3_evm
basically becomes the defconfig.

That doesn't seem un-reasonable. Although the solver to me seems more
elegant and we're getting the solver for some other reasons it seems
(unrelated to this defconfig issue).

Daniel


--
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/