> This patch could be using the cpu_possible_map instead of our own. > I was reluctant to do that, but there is nothing that prevents it. > Does anybody have an opinion? I hate to see duplication ... your new "early_cpu_possible_map" should just end up with the same contents as "cpu_possible_map" ... won't it? Is there some downside to using your new code to initialize the existing cpu_possible_map? -Tony - To unsubscribe from this list: send the line "unsubscribe linux-ia64" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
|