The patch titled
cpumask add highest_possible_node_id fix
has been added to the -mm tree. Its filename is
cpumask-add-highest_possible_node_id-fix.patch
See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find
out what to do about this
------------------------------------------------------
Subject: cpumask add highest_possible_node_id fix
From: Paul Jackson <pj@xxxxxxx>
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@xxxxxxx>
Cc: Greg Banks <gnb@xxxxxxxxxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxx>
---
lib/cpumask.c | 2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
diff -puN lib/cpumask.c~cpumask-add-highest_possible_node_id-fix lib/cpumask.c
--- a/lib/cpumask.c~cpumask-add-highest_possible_node_id-fix
+++ a/lib/cpumask.c
@@ -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;
}
_
Patches currently in -mm which might be from pj@xxxxxxx are
origin.patch
cpuset-top_cpuset-tracks-hotplug-changes-to-node_online_map.patch
cpuset-top_cpuset-tracks-hotplug-changes-to-node_online_map-fix.patch
cpuset-top_cpuset-tracks-hotplug-changes-to-node_online_map-fix-2.patch
cpuset-hotunplug-cpus-and-mems-in-all-cpusets.patch
cpuset-fix-obscure-attach_task-vs-exiting-race.patch
cpumask-add-highest_possible_node_id-fix.patch
sched-force-sbin-init-off-isolated-cpus.patch
sched-introduce-child-field-in-sched_domain.patch
sched-cleanup-sched_group-cpu_power-setup.patch
-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
