Re: [PATCH -tip/cpus4096-v2] cpumask: fix cpumask of call_function_data

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Ingo Molnar
Date: Monday, October 27, 2008 - 5:55 am

* Rusty Russell <rusty@rustcorp.com.au> wrote:


ok - applied it to tip/cpus4096-v2, thanks Rusty!

If there's any chance for this in v2.6.28 then only if we disable the 
dynamic API branch altogether [CONFIG_MAXCPUS] and keep that for 
v2.6.29. This means we'd bring in the API changes which should have 
trivial impact only - and none of the riskier changes.

Hm?

Andrew, have we missed the boat on this?

	Ingo
--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[PATCH -tip/cpus4096-v2] cpumask: fix cpumask of call_func ..., Hiroshi Shimamoto, (Thu Oct 23, 9:47 pm)
Re: [PATCH -tip/cpus4096-v2] cpumask: fix cpumask of call_ ..., Hiroshi Shimamoto, (Fri Oct 24, 2:46 pm)
Re: [PATCH -tip/cpus4096-v2] cpumask: fix cpumask of call_ ..., Ingo Molnar, (Mon Oct 27, 5:55 am)
Re: [PATCH -tip/cpus4096-v2] cpumask: fix cpumask of call_ ..., Hiroshi Shimamoto, (Mon Oct 27, 4:07 pm)
Re: [PATCH -tip/cpus4096-v2] cpumask: fix cpumask , Rusty Russell, (Mon Oct 27, 5:46 pm)
Re: [PATCH -tip/cpus4096-v2] cpumask: fix cpumask of call_ ..., Hiroshi Shimamoto, (Thu Oct 30, 10:44 am)