From: Adrian Bunk <bunk@stusta.de>
To: Andrew Morton <akpm@zip.com.au>
Cc: rmk@arm.linux.org.uk, linux-arm-kernel@lists.arm.linux.org.uk,
linux-kernel@vger.kernel.org
Subject: [2.6 patch] arm: NR_CPUS: use range
Date: Sun, 6 Feb 2005 16:18:40 +0100 [thread overview]
Message-ID: <20050206151840.GQ3129@stusta.de> (raw)
This patch uses range for NR_CPUS on arm (the same is already done on
all other architectures).
Signed-off-by: Adrian Bunk <bunk@stusta.de>
---
This patch was already sent on:
- 15 Jan 2005
--- linux-2.6.11-rc1-mm1-full/arch/arm/Kconfig.old 2005-01-15 07:34:47.000000000 +0100
+++ linux-2.6.11-rc1-mm1-full/arch/arm/Kconfig 2005-01-15 07:38:24.000000000 +0100
@@ -286,6 +286,7 @@
config NR_CPUS
int "Maximum number of CPUs (2-32)"
+ range 2 32
depends on SMP
default "4"
next reply other threads:[~2005-02-06 15:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-06 15:18 Adrian Bunk [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-01-15 6:39 [2.6 patch] arm: NR_CPUS: use range 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=20050206151840.GQ3129@stusta.de \
--to=bunk@stusta.de \
--cc=akpm@zip.com.au \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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