From: Anton Blanchard <anton@samba.org>
To: Matthew Dobson <colpatch@us.ibm.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
William Lee Irwin III <wli@holomorphy.com>,
Martin Bligh <mjbligh@us.ibm.com>
Subject: Re: [rfc][patch] MAX_NR_NODES vs. MAX_NUMNODES
Date: Fri, 1 Nov 2002 13:21:14 +1100 [thread overview]
Message-ID: <20021101022114.GA728@krispykreme> (raw)
In-Reply-To: <3DB8927E.5090909@us.ibm.com>
Hi Matt,
> This patch
> 1) Gets rid of the include/asm-xxx/numnodes.h files
> 2) Defines MAX_NR_NODES to the appropriate per-arch value in
> include/asm-xxx/param.h
> 3) changes all remaining occurences MAX_NUMNODES to MAX_NR_NODES
> throughout the kernel
Looks good for ppc64.
Anton (using 20 hours of flights trying to catch up on email)
prev parent reply other threads:[~2002-11-01 3:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-25 0:38 [rfc][patch] MAX_NR_NODES vs. MAX_NUMNODES Matthew Dobson
2002-10-25 9:00 ` Russell King
2002-10-28 19:47 ` Matthew Dobson
2002-10-28 21:37 ` Russell King
2002-10-28 23:18 ` Matthew Dobson
2002-11-01 2:21 ` Anton Blanchard [this message]
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=20021101022114.GA728@krispykreme \
--to=anton@samba.org \
--cc=colpatch@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjbligh@us.ibm.com \
--cc=wli@holomorphy.com \
/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).