From: Adrian Bunk <bunk@kernel.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Sam Ravnborg <sam@ravnborg.org>,
Harvey Harrison <harvey.harrison@gmail.com>,
tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
linux-kernel@vger.kernel.org
Subject: Re: [2.6.24 patch] x86: allow 64bit setting in Kconfig
Date: Fri, 18 Jan 2008 14:09:58 +0200 [thread overview]
Message-ID: <20080118120958.GB19723@does.not.exist> (raw)
In-Reply-To: <20080118120248.GA11044@elte.hu>
On Fri, Jan 18, 2008 at 01:02:48PM +0100, Ingo Molnar wrote:
>
> * Sam Ravnborg <sam@ravnborg.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"
At least for me it's clear what the former does while I had to try the
latter for understanding what it does exactly...
> Ingo
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2008-01-18 12:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-17 21:43 [2.6.24 patch] x86: allow 64bit setting in Kconfig Adrian Bunk
2008-01-18 10:44 ` Ingo Molnar
2008-01-18 10:50 ` Harvey Harrison
2008-01-18 11:37 ` Sam Ravnborg
2008-01-18 12:02 ` Ingo Molnar
2008-01-18 12:09 ` Adrian Bunk [this message]
2008-01-18 11:48 ` Ingo Molnar
2008-01-18 17:00 ` Ingo Molnar
2008-01-18 17:26 ` Adrian Bunk
2008-01-18 21:06 ` Ingo Molnar
2008-01-18 21:23 ` Adrian Bunk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080118120958.GB19723@does.not.exist \
--to=bunk@kernel.org \
--cc=harvey.harrison@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=sam@ravnborg.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.