From: Paul Jackson <pj@sgi.com>
To: linux-kernel@vger.kernel.org
Cc: mbligh@aracnet.com, akpm@osdl.org, wli@holomorphy.com,
haveblue@us.ibm.com, colpatch@us.ibm.com
Subject: [PATCH] mask ADT: fix nodes_complement usage - x86_64 [22/22]
Date: Mon, 29 Mar 2004 04:16:28 -0800 [thread overview]
Message-ID: <20040329041628.68d82db1.pj@sgi.com> (raw)
Patch_22_of_22 - Fix nodes_complement call - it's a dyadic macro.
One bit of code in Matthew's Patch 5 of 7 also had a
nodes_complement call - convert it to two arg form.
diffstat Patch_22_of_22:
k8topology.c | 3 ++-
1 files changed, 2 insertions(+), 1 deletion(-)
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet 1.1728 -> 1.1729
# arch/x86_64/mm/k8topology.c 1.10 -> 1.11
#
# The following is the BitKeeper ChangeSet Log
# --------------------------------------------
# 04/03/29 pj@sgi.com 1.1729
# Fix nodes_complement call - it's a dyadic macro.
# --------------------------------------------
#
diff -Nru a/arch/x86_64/mm/k8topology.c b/arch/x86_64/mm/k8topology.c
--- a/arch/x86_64/mm/k8topology.c Mon Mar 29 01:41:13 2004
+++ b/arch/x86_64/mm/k8topology.c Mon Mar 29 01:41:13 2004
@@ -163,7 +163,8 @@
CPUs, as the number of CPUs is not known yet.
We round robin the existing nodes. */
rr = first_node(node_online_map);
- nodemask_t node_offline_map = nodes_complement(node_online_map);
+ nodemask_t node_offline_map;
+ nodes_complement(node_offline_map, node_online_map);
for_each_node_mask(i, node_offline_map) {
node_data[i] = node_data[rr];
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.650.933.1373
reply other threads:[~2004-03-29 13:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20040329041628.68d82db1.pj@sgi.com \
--to=pj@sgi.com \
--cc=akpm@osdl.org \
--cc=colpatch@us.ibm.com \
--cc=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.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