kbuild: Spelling/grammar fixes for config DEBUG_SECTION_MISMATCH

Including additional fixes from Randy Dunlap <randy.dunlap@oracle.com> Signed-off-by: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com> Signed-off-by: Sam Ravnborg <sam@ravnborg.org>

kbuild: Spelling/grammar fixes for config DEBUG_SECTION_MISMATCH
Including additional fixes from Randy Dunlap <randy.dunlap@oracle.com> Signed-off-by: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com> Signed-off-by: Sam Ravnborg <sam@ravnborg.org>
Geert Uytterhoeven · Sam Ravnborg
1 parent 470a81ae15
Showing 1 changed file with 6 additions and 6 deletions Side-by-side Diff
lib/Kconfig.debug
@@ -90,19 +90,19 @@
 	  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
-	  kernel build but enabling this options will in addition
+	  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 option will in addition
 	  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
+	    function we would lose the section information and thus
 	    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
+	    lose valueble information about where the mismatch was
 	    introduced.
 	    Running the analysis for each module/built-in.o file
 	    will tell where the mismatch happens much closer to the
...	...	@@ -90,19 +90,19 @@
90	90	most likely result in an oops.
91	91	In the code functions and variables are annotated with
92	92	__init, __devinit etc. (see full list in include/linux/init.h)
93		- which result in the code/data being placed in specific sections.
94		- The section mismatch anaylsis are always done after a full
95		- kernel build but enabling this options will in addition
	93	+ which results in the code/data being placed in specific sections.
	94	+ The section mismatch analysis is always done after a full
	95	+ kernel build but enabling this option will in addition
96	96	do the following:
97	97	- Add the option -fno-inline-functions-called-once to gcc
98	98	When inlining a function annotated __init in a non-init
99		- function we would loose the section information and thus
	99	+ function we would lose the section information and thus
100	100	the analysis would not catch the illegal reference.
101		- This options tell gcc to inline less but will also
	101	+ This option tells gcc to inline less but will also
102	102	result in a larger kernel.
103	103	- Run the section mismatch analysis for each module/built-in.o
104	104	When we run the section mismatch analysis on vmlinux.o we
105		- looses valueable information about where the mismatch was
	105	+ lose valueble information about where the mismatch was
106	106	introduced.
107	107	Running the analysis for each module/built-in.o file
108	108	will tell where the mismatch happens much closer to the