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: <alpine.LFD.2.00.1006031153420.8175@i5.linux-foundation.org>
Date:	Thu, 3 Jun 2010 11:56:53 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Russell King <rmk@....linux.org.uk>
cc:	Kevin Hilman <khilman@...prootsystems.com>,
	Daniel Walker <dwalker@...eaurora.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-arm-msm@...r.kernel.org
Subject: Re: ARM defconfig files

On Thu, 3 Jun 2010, Russell King wrote:
> 
> No amount of reorganising the Kconfig files into a heirarchial manner
> (which they already are) helps.  Not one bit.  Because they already are.
> That's not where the problem is.

I don't think you read the whole thread.

Earlier on, I explained exactly what I wanted: just add some "select" 
statements to pickt he things you need per the particular target 
configuration. You seem to have missed that part.

In other words, you _can_ encode the information that is in the 
xyz_defconfig files by doing it in Kconfig.xyz files instead. But you do 
it in a human-readable manner. And the hierarchical thing is absolutely 
required for that - otherwise you'd end up with just another form of the 
current xyz_defconfig.

See?

In other words, you should be able to basically use "make allnoconfig" 
together with a Kconfig.xyz file input to select _exactly_ the pieces you 
need, and nothing else.

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