On Sat, Jul 07, 2007 at 10:15:58PM +0530, Satyam Sharma wrote:
> sh_machine_vector structures throughout arch/sh/boards/ are marked
> __initmv so that they go to the .machvec.init section, when SH_GENERIC ||
> SH_UNKNOWN. But when !SH_GENERIC && !SH_UNKNOWN, __initmv is not defined,
> so all the ma
On Sat, 07 Jul 2007 22:17:22 +0530 Satyam Sharma wrote:
> This:
>
> WARNING: kernel/built-in.o(.text+0x16910): Section mismatch:
> reference to .init.text: (between 'kthreadd' and 'init_waitqueue_head')
>
> comes because kernel/kthread.c:kthreadd() is not __init but calls
> kthreadd_setup() whic
sh_machine_vector structures throughout arch/sh/boards/ are marked
__initmv so that they go to the .machvec.init section, when SH_GENERIC ||
SH_UNKNOWN. But when !SH_GENERIC && !SH_UNKNOWN, __initmv is not defined,
so all the machine vector structures go to the .data section. But, all
the .mv_setup
This:
WARNING: kernel/built-in.o(.text+0x16910): Section mismatch:
reference to .init.text: (between 'kthreadd' and 'init_waitqueue_head')
comes because kernel/kthread.c:kthreadd() is not __init but calls
kthreadd_setup() which is __init. But this is ok, because kthreadd_setup()
is only ever call
sh_machine_vector structures throughout arch/sh/boards/ are marked
__initmv so that they go to the .machvec.init section, when SH_GENERIC ||
SH_UNKNOWN. But when !SH_GENERIC && !SH_UNKNOWN, __initmv is not defined,
so all the machine vector structures go to the .data section. But, all
the .mv_setup
5 matches
Mail list logo