On Wed, 30 Jan 2008 11:13:23 +0100 (CET) Geert Uytterhoeven wrote: > kbuild: Spelling/grammar fixes for config DEBUG_SECTION_MISMATCH > > Signed-off-by: Geert Uytterhoeven <Geert.Uytterhoeven@xxxxxxxxxxx> > --- > lib/Kconfig.debug | 8 ++++---- > 1 file changed, 4 insertions(+), 4 deletions(-) > > --- a/lib/Kconfig.debug > +++ b/lib/Kconfig.debug > @@ -90,19 +90,19 @@ config DEBUG_SECTION_MISMATCH > most likely result in an oops. > In the code functions and variables are annotated with > __init, __devinit etc. (see full list in include/linux/init.h) > - which result in the code/data being placed in specific sections. > - The section mismatch anaylsis are always done after a full > + which results in the code/data being placed in specific sections. > + The section mismatch analysis is always done after a full > kernel build but enabling this options will in addition option > do the following: > - Add the option -fno-inline-functions-called-once to gcc > When inlining a function annotated __init in a non-init > function we would loose the section information and thus lose > the analysis would not catch the illegal reference. > - This options tell gcc to inline less but will also > + This option tells gcc to inline less but will also > result in a larger kernel. > - Run the section mismatch analysis for each module/built-in.o > When we run the section mismatch analysis on vmlinux.o we > - looses valueable information about where the mismatch was > + loose valueable information about where the mismatch was lose valuable > introduced. > Running the analysis for each module/built-in.o file > will tell where the mismatch happens much closer to the Thanks. I had a note to myself to do this as well. --- ~Randy - To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
