4 files changed, 10 insertions, 10 deletions

diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index 0d8a5a4a789d..0d385be682db 100644
--- a/lib/Kconfig.debug
+++ b/lib/Kconfig.debug
@@ -81,7 +81,7 @@ config HEADERS_CHECK
 
 config DEBUG_SECTION_MISMATCH
         bool "Enable full Section mismatch analysis"
-        default n
+        depends on UNDEFINED
         help
           The section mismatch analysis checks if there are illegal
           references from one section to another section.
@@ -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
-          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
diff --git a/lib/crc32.c b/lib/crc32.c
index d2c2f257bedd..49d1c9e3ce38 100644
--- a/lib/crc32.c
+++ b/lib/crc32.c
@@ -348,7 +348,7 @@ EXPORT_SYMBOL(crc32_be);
  * but again the multiple of the polynomial to subtract depends only on
  * the high bits, the high 8 bits in this case.  
  *
- * The multile we need in that case is the low 32 bits of a 40-bit
+ * The multiple we need in that case is the low 32 bits of a 40-bit
  * value whose high 8 bits are given, and which is a multiple of the
  * generator polynomial.  This is simply the CRC-32 of the given
  * one-byte message.
diff --git a/lib/kobject.c b/lib/kobject.c
index 1d63ead1815e..d784daeb8571 100644
--- a/lib/kobject.c
+++ b/lib/kobject.c
@@ -637,7 +637,7 @@ struct kobject *kobject_create(void)
  * @name: the name for the kset
  * @parent: the parent kobject of this kobject, if any.
  *
- * This function creates a kset structure dynamically and registers it
+ * This function creates a kobject structure dynamically and registers it
  * with sysfs.  When you are finished with this structure, call
  * kobject_put() and the structure will be dynamically freed when
  * it is no longer being used.
diff --git a/lib/zlib_deflate/defutil.h b/lib/zlib_deflate/defutil.h
index d9feaf638608..6b15a909ca3f 100644
--- a/lib/zlib_deflate/defutil.h
+++ b/lib/zlib_deflate/defutil.h
@@ -164,7 +164,7 @@ typedef struct deflate_state {
     int nice_match; /* Stop searching when current match exceeds this */
 
                 /* used by trees.c: */
-    /* Didn't use ct_data typedef below to supress compiler warning */
+    /* Didn't use ct_data typedef below to suppress compiler warning */
     struct ct_data_s dyn_ltree[HEAP_SIZE];   /* literal and length tree */
     struct ct_data_s dyn_dtree[2*D_CODES+1]; /* distance tree */
     struct ct_data_s bl_tree[2*BL_CODES+1];  /* Huffman tree for bit lengths */