> > > otoh, if only one .c file will ever call this function then I think that > > > all problems are solved by > > > > > > a) moving the above ifdeffery into the .c file > > > b) adding a comment explaining which arch file must provide the override > > > c) directly including that file from within the .c file. > > > > I can definitely do that. I have no problem either way. I can add to all > > archs too, it's just that whatever way I choose, some people won't be > > happy with it :-) > > > > Anyway, I'll move the ifdeferry to init/main.c then. > > Thanks ;) > > I'm still wounded by my recent encounter with set_softirq_pending() > and or_softirq_pending(). Well, looking there, I saw we already used weak symbols for that so what about the patch below ? If you're ok, I'll re-send with appropriate sob & adapted powerpc part. Cheers, Ben. Index: linux-work/init/main.c =================================================================== --- linux-work.orig/init/main.c 2008-03-26 10:39:25.000000000 +1100 +++ linux-work/init/main.c 2008-04-18 13:10:35.000000000 +1000 @@ -504,6 +504,10 @@ void __init __attribute__((weak)) smp_se { } +void __init __attribute__((weak) thread_info_cache_init(void) +{ +} + asmlinkage void __init start_kernel(void) { char * command_line; @@ -623,6 +627,7 @@ asmlinkage void __init start_kernel(void if (efi_enabled) efi_enter_virtual_mode(); #endif + thread_info_cache_init(); fork_init(num_physpages); proc_caches_init(); buffer_init(); Index: linux-work/include/linux/sched.h =================================================================== --- linux-work.orig/include/linux/sched.h 2008-04-02 09:47:56.000000000 +1100 +++ linux-work/include/linux/sched.h 2008-04-18 13:11:10.000000000 +1000 @@ -1893,6 +1893,8 @@ static inline unsigned long *end_of_stac #endif +extern void thread_info_cache_init(void); + /* set thread flags in other task's structures * - see asm/thread_info.h for TIF_xxxx flags available */ -- To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html