linux-kernel - Re: [2.6.24 patch] x86: allow 64bit setting in Kconfig

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: <20080118120248.GA11044@elte.hu>
Date:	Fri, 18 Jan 2008 13:02:48 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Sam Ravnborg <sam@...nborg.org>
Cc:	Harvey Harrison <harvey.harrison@...il.com>,
	Adrian Bunk <bunk@...nel.org>, tglx@...utronix.de,
	mingo@...hat.com, hpa@...or.com, linux-kernel@...r.kernel.org
Subject: Re: [2.6.24 patch] x86: allow 64bit setting in Kconfig


* Sam Ravnborg <sam@...nborg.org> wrote:

> > Style question, would the following be preferred?
> > 
> > config 64BIT
> > 	def_bool ARCH = "x86_64"
> > 	prompt "64-bit kernel"
> > 	help...
> 
> No.
> It is most common to let the prompt follow the type and not
> as a separate property.

hm, ok. I guess there's not much cleanliness difference between:

    bool "64-bit kernel"
    default ARCH = "x86_64"

and:

    def_bool ARCH = "x86_64"
    prompt "64-bit kernel"

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