Nick Piggin <[email protected]> wrote: > > for_each_cpu has always meant for > each possible CPU. That was the most long-winded ack I've ever seen ;) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- References:
- [PATCH] for_each_possible_cpu [1/19] defines for_each_possible_cpu
- From: KAMEZAWA Hiroyuki <[email protected]>
- Re: [PATCH] for_each_possible_cpu [1/19] defines for_each_possible_cpu
- From: Nick Piggin <[email protected]>
- Re: [PATCH] for_each_possible_cpu [1/19] defines for_each_possible_cpu
- From: KAMEZAWA Hiroyuki <[email protected]>
- Re: [PATCH] for_each_possible_cpu [1/19] defines for_each_possible_cpu
- From: Nick Piggin <[email protected]>
- Re: [PATCH] for_each_possible_cpu [1/19] defines for_each_possible_cpu
- From: KAMEZAWA Hiroyuki <[email protected]>
- Re: [PATCH] for_each_possible_cpu [1/19] defines for_each_possible_cpu
- From: Nick Piggin <[email protected]>
- [PATCH] for_each_possible_cpu [1/19] defines for_each_possible_cpu
- Prev by Date: Re: [PATCH 10 of 20] ipath - support for userspace apps using core driver
- Next by Date: 2.6.16-rc6-rt7
- Previous by thread: Re: [PATCH] for_each_possible_cpu [1/19] defines for_each_possible_cpu
- Next by thread: Re: [PATCH] for_each_possible_cpu [1/19] defines for_each_possible_cpu
- Index(es):
 |