1 files changed, 6 insertions, 6 deletions
diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index d090d7201086..0d385be682db 100644
--- 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.
+          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:
          - 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

diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug index d090d7201086..0d385be682db 100644 --- a/lib/Kconfig.debug +++ b/lib/Kconfig.debug
@@ -90,19 +90,19 @@ config DEBUG_SECTION_MISMATCH
90	most likely result in an oops.	90	most likely result in an oops.
91	In the code functions and variables are annotated with	91	In the code functions and variables are annotated with
92	__init, __devinit etc. (see full list in include/linux/init.h)	92	__init, __devinit etc. (see full list in include/linux/init.h)
93	which result in the code/data being placed in specific sections.	93	which results in the code/data being placed in specific sections.
94	The section mismatch anaylsis are always done after a full	94	The section mismatch analysis is always done after a full
95	kernel build but enabling this options will in addition	95	kernel build but enabling this option will in addition
96	do the following:	96	do the following:
97	- Add the option -fno-inline-functions-called-once to gcc	97	- Add the option -fno-inline-functions-called-once to gcc
98	When inlining a function annotated __init in a non-init	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	the analysis would not catch the illegal reference.	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	result in a larger kernel.	102	result in a larger kernel.
103	- Run the section mismatch analysis for each module/built-in.o	103	- Run the section mismatch analysis for each module/built-in.o
104	When we run the section mismatch analysis on vmlinux.o we	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	introduced.	106	introduced.
107	Running the analysis for each module/built-in.o file	107	Running the analysis for each module/built-in.o file
108	will tell where the mismatch happens much closer to the	108	will tell where the mismatch happens much closer to the