From: Matthew Wilcox <willy@debian.org>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] Kconfig cleanup, part 1
Date: Sat, 17 Jan 2004 00:45:02 +0000 [thread overview]
Message-ID: <20040117004502.GB16779@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <200401161136.37066.bjorn.helgaas@hp.com>
On Fri, Jan 16, 2004 at 05:22:36PM -0700, Bjorn Helgaas wrote:
> Here comes the revised entire patch:
[...]
> config 64BIT
> - def_bool y
> + bool
> + default y
>
Why make this change? def_bool is shorter and (to my mind ;-) neater.
> config ITANIUM_BSTEP_SPECIFIC
> - bool "Enable Itanium B-step specific code"
> + bool "Itanium B-step specific code"
> depends on ITANIUM
> help
> Select this option to build a kernel for an Itanium prototype system
> @@ -198,38 +192,30 @@
>
> # align cache-sensitive data to 64 bytes
> config MCKINLEY_ASTEP_SPECIFIC
> - bool "Enable McKinley A-step specific code"
> + bool "McKinley A-step specific code"
> depends on MCKINLEY
> help
> Select this option to build a kernel for an IA-64 McKinley prototype
> system with any A-stepping CPU.
>
> config MCKINLEY_A0_SPECIFIC
> - bool "Enable McKinley A0/A1-step specific code"
> + bool "McKinley A0/A1-step specific code"
> depends on MCKINLEY_ASTEP_SPECIFIC
> help
> Select this option to build a kernel for an IA-64 McKinley prototype
> system with an A0 or A1 stepping CPU.
Possibly we should kill these options and the code they enable now. Is
anyone still using A-step McKinleys and B-step Merceds?
> config NUMA
> - bool "Enable NUMA support" if IA64_GENERIC || IA64_DIG || IA64_HP_ZX1
> - default y if IA64_SGI_SN2 || IA64_GENERIC
> + bool "NUMA support"
> + depends on !IA64_HP_SIM
> + default y if IA64_SGI_SN2
Nice change, much more clear.
--
"Next the statesmen will invent cheap lies, putting the blame upon
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince
himself that the war is just, and will thank God for the better sleep
he enjoys after this process of grotesque self-deception." -- Mark Twain
next prev parent reply other threads:[~2004-01-17 0:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-16 18:36 [PATCH] Kconfig cleanup, part 1 Bjorn Helgaas
2004-01-16 19:16 ` David Mosberger
2004-01-16 21:39 ` Peter Chubb
2004-01-16 22:32 ` Bjorn Helgaas
2004-01-16 23:35 ` Matthew Wilcox
2004-01-17 0:03 ` Bjorn Helgaas
2004-01-17 0:18 ` Matthew Wilcox
2004-01-17 0:22 ` Bjorn Helgaas
2004-01-17 0:45 ` Matthew Wilcox [this message]
2004-01-17 0:59 ` David Mosberger
2004-01-20 17:11 ` Bjorn Helgaas
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=20040117004502.GB16779@parcelfarce.linux.theplanet.co.uk \
--to=willy@debian.org \
--cc=linux-ia64@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox