linux-kernel - Re: [PATCH] 9p: fix compile error if !CONFIG

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]

Date:	Fri, 28 Sep 2007 07:34:49 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Nick Piggin <nickpiggin@...oo.com.au>
cc:	Andrew Morton <akpm@...ux-foundation.org>,
	kbuild-devel@...ts.sourceforge.net,
	Andreas Herrmann <aherrman@...or.de>,
	Eric Van Hensbergen <ericvh@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] 9p: fix compile error if !CONFIG_SYSCTL



On Fri, 28 Sep 2007, Nick Piggin wrote:
> >
> > God I hate select.
> 
> IMO a better implementation would result in a notification / confirmation of
> turning on new items, and the ability to deselect options which will also
> confirm to deselect dependants. Like most other systems that have similar
> problem to solve.

Actually, the *really* nice thing to do would be to just add the reason 
something got enabled into the ".config" file.

IOW, wouldn't it be nice if the .config file just said

	...
	CONFIG_ACPI=y		# selected by X86_64_ACPI_NUMA
	CONFIG_ACPI_PROCFS=y	# user choice
	...

etc, since the config process actually does know these things?

That way, there's always a fairly straightforward way to see why some 
configuration is the way it is (and the .config file is not only useful 
for "make oldconfig", it's also what normally gets passed around for bug 
reports, and is part of distro kernel packages etc, so it would seem to be 
the right place, no?)

		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/