From: Avi Kivity <avi@argo.co.il>
To: Christoph Lameter <clameter@sgi.com>
Cc: akpm@osdl.org, linux-mm@kvack.org
Subject: Re: [PATCH]Convert highest_possible_processor_id to nr_cpu_ids
Date: Fri, 02 Feb 2007 18:16:51 +0200 [thread overview]
Message-ID: <45C363F3.2000207@argo.co.il> (raw)
In-Reply-To: <Pine.LNX.4.64.0701291437590.1067@schroedinger.engr.sgi.com>
Christoph Lameter wrote:
> This follows up on the patch to create nr_node_ids... Patch against
> 2.6.20-rc6 + Andrew's fix for mistakenly replacing
> highest_possible_processor_id() with nr_node_ids.
>
>
>
>
[!CONFIG_SMP]
> -#define highest_possible_processor_id() 0
> +#define nr_cpu_ids 0
>
Shouldn't this be 1?
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-02-02 16:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-29 22:39 [PATCH]Convert highest_possible_processor_id to nr_cpu_ids Christoph Lameter
2007-02-02 16:16 ` Avi Kivity [this message]
2007-02-02 19:19 ` Christoph Lameter
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=45C363F3.2000207@argo.co.il \
--to=avi@argo.co.il \
--cc=akpm@osdl.org \
--cc=clameter@sgi.com \
--cc=linux-mm@kvack.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;
as well as URLs for NNTP newsgroup(s).