Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit d6fbfa4f authored by Geert Uytterhoeven's avatar Geert Uytterhoeven Committed by Sam Ravnborg
Browse files

kbuild: Spelling/grammar fixes for config DEBUG_SECTION_MISMATCH



Including additional fixes from Randy Dunlap <randy.dunlap@oracle.com>

Signed-off-by: default avatarGeert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>
Signed-off-by: default avatarSam Ravnborg <sam@ravnborg.org>
parent 470a81ae
Loading
Loading
Loading
Loading
+6 −6
Original line number Original line Diff line number Diff line
@@ -90,19 +90,19 @@ config DEBUG_SECTION_MISMATCH
	  most likely result in an oops.
	  most likely result in an oops.
	  In the code functions and variables are annotated with
	  In the code functions and variables are annotated with
	  __init, __devinit etc. (see full list in include/linux/init.h)
	  __init, __devinit etc. (see full list in include/linux/init.h)
	  which result in the code/data being placed in specific sections.
	  which results in the code/data being placed in specific sections.
	  The section mismatch anaylsis are always done after a full
	  The section mismatch analysis is always done after a full
	  kernel build but enabling this options will in addition
	  kernel build but enabling this option will in addition
	  do the following:
	  do the following:
	  - Add the option -fno-inline-functions-called-once to gcc
	  - Add the option -fno-inline-functions-called-once to gcc
	    When inlining a function annotated __init in a non-init
	    When inlining a function annotated __init in a non-init
	    function we would loose the section information and thus
	    function we would lose the section information and thus
	    the analysis would not catch the illegal reference.
	    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.
	    result in a larger kernel.
	  - Run the section mismatch analysis for each module/built-in.o
	  - Run the section mismatch analysis for each module/built-in.o
	    When we run the section mismatch analysis on vmlinux.o we
	    When we run the section mismatch analysis on vmlinux.o we
	    looses valueable information about where the mismatch was
	    lose valueble information about where the mismatch was
	    introduced.
	    introduced.
	    Running the analysis for each module/built-in.o file
	    Running the analysis for each module/built-in.o file
	    will tell where the mismatch happens much closer to the
	    will tell where the mismatch happens much closer to the