Messages in this thread | | | Date | Fri, 28 Apr 2006 16:23:02 -0700 | From | Andrew Morton <> | Subject | Re: Linux 2.6.17-rc2 - notifier chain problem? |
| |
Chandra Seetharaman <sekharan@us.ibm.com> wrote: > > Looks like the patches I provided is a step backward from where Ashok & > Andrew were taking the register_cpu_notifier stuff to. > > After some discussions with Ashok we both think the following would be > the right direction: > 1 revert the changes i pushed recently > 2 make all usages of register_cpu_notifier to be _init and > __initdata (if hotplug cpu is defined these are removed) > 3 export the symbols register_cpu_notifier and > unregister_cpu_notifier only in CONFIG_HOTPLUG_CPU is defined > 4 move the hot plug cpu based usages of register_cpu_notifier > inside #ifdef CONFIG_HOTPLUF_CPU(like xfs's usage). > > I have few questions: > - any problems with the above direction (mainly 3) ? > - Should we proceed in this direction ? > - is it too late for 2.6.17 ? if not late how much time do we have ?
hm. I'm leaning more towards doing something expedient and obvious for 2.6.17. It's pretty late in the cycle, and the only downside is the loss of a kbyte or two. Plus I'll be at linuxtag next week and won't be around to help out.
So if it's OK, can we do something minimal, revisit it after 2.6.17? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |