public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: kbuild <linux-kbuild@vger.kernel.org>
Cc: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>
Subject: [PATCH] kbuild: Spelling/grammar fixes for config DEBUG_SECTION_MISMATCH
Date: Sat,  2 Feb 2008 21:46:36 +0100	[thread overview]
Message-ID: <1201985204-26589-2-git-send-email-sam@ravnborg.org> (raw)
In-Reply-To: <20080202203503.GA26415@uranus.ravnborg.org>

From: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>

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>
---
 lib/Kconfig.debug |   12 ++++++------
 1 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index d090d72..0d385be 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.
-	  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
-- 
1.5.4.rc3.14.g44397


  parent reply	other threads:[~2008-02-02 20:46 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-02 20:35 [REVIEW for merge] kbuild updates including silence of section mismatch check Sam Ravnborg
2008-02-02 20:46 ` [PATCH] Remove __INIT_REFOK and __INITDATA_REFOK Sam Ravnborg
2008-02-02 20:46 ` Sam Ravnborg [this message]
2008-02-02 20:46 ` [PATCH] kbuild: add svn revision information to setlocalversion Sam Ravnborg
2008-02-02 20:46 ` [PATCH] kconfig: mark config as changed when loading an alternate config Sam Ravnborg
2008-02-02 20:46 ` [PATCH] kconfig: ignore select of unknown symbol Sam Ravnborg
2008-02-02 20:46 ` [PATCH] Fix ARM to play nicely with generic Instrumentation menu Sam Ravnborg
2008-02-02 20:46 ` [PATCH] Create arch/Kconfig Sam Ravnborg
2008-02-02 20:46 ` [PATCH] Add HAVE_OPROFILE Sam Ravnborg
2008-02-02 20:46 ` [PATCH] Add HAVE_KPROBES Sam Ravnborg
2008-02-02 20:46 ` [PATCH] Move Kconfig.instrumentation to arch/Kconfig and init/Kconfig Sam Ravnborg
2008-02-02 21:25 ` [REVIEW for merge] kbuild updates including silence of section mismatch check Frans Pop
2008-02-02 21:30   ` Sam Ravnborg
2008-02-03  3:30     ` Bryan Wu
2008-02-03  6:13     ` [PATCH try#2 ] kbuild: add svn revision information to setlocalversion Bryan Wu
2008-02-03 10:04       ` Sam Ravnborg
2008-02-02 22:37 ` [Additional PATCH] kbuild: do not warn about __*init/__*exit symbols being exported Sam Ravnborg
2008-02-05 10:38 ` [REVIEW for merge] kbuild updates including silence of section mismatch check Geert Uytterhoeven
2008-02-06 20:58   ` Sam Ravnborg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1201985204-26589-2-git-send-email-sam@ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=Geert.Uytterhoeven@sonycom.com \
    --cc=linux-kbuild@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox