linux-kernel - [PATCH] cpumask add highest_possible_node

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-Id: <20060927085429.32218.64893.sendpatchset@sam.engr.sgi.com>
Date:	Wed, 27 Sep 2006 01:54:29 -0700
From:	Paul Jackson <pj@....com>
To:	Andrew Morton <akpm@...l.org>
Cc:	Greg Banks <gnb@...bourne.sgi.com>, Paul Jackson <pj@....com>,
	linux-kernel@...r.kernel.org
Subject: [PATCH] cpumask add highest_possible_node_id fix

Fix typo in lib/cpumask.c - looks like a cut+paste forgot
to change a cpu macro call to a node macro call.  This
typo caused the following build warnings:

lib/cpumask.c: In function `highest_possible_node_id':
lib/cpumask.c:56: warning: passing arg 1 of `__first_cpu' from incompatible pointer type
lib/cpumask.c:56: warning: passing arg 2 of `__next_cpu' from incompatible pointer type   

Signed-off-by: Paul Jackson <pj@....com>

---

 lib/cpumask.c |    2 +-
 1 files changed, 1 insertion(+), 1 deletion(-)

--- 2.6.18-rc7-mm1.orig/lib/cpumask.c	2006-09-26 16:25:57.000000000 -0700
+++ 2.6.18-rc7-mm1/lib/cpumask.c	2006-09-27 01:38:17.000000000 -0700
@@ -53,7 +53,7 @@ int highest_possible_node_id(void)
 	unsigned int node;
 	unsigned int highest = 0;
 
-	for_each_cpu_mask(node, node_possible_map)
+	for_each_node_mask(node, node_possible_map)
 		highest = node;
 	return highest;
 }

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@....com> 1.925.600.0401
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/