mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: [ptxdist] [PATCH] kernel: don't add DEBUG_SECTION_MISMATCH=y by default
Date: Tue,  9 Jun 2015 16:12:21 +0200	[thread overview]
Message-ID: <1433859141-16035-1-git-send-email-u.kleine-koenig@pengutronix.de> (raw)

DEBUG_SECTION_MISMATCH is a development option that shouldn't be used
in production settings so IMHO it's not sensible to add it as default
setting.

Moreover do some minor wording cleanups.

Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
---
 platforms/kernel.in | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/platforms/kernel.in b/platforms/kernel.in
index 2b44ec1e2d40..9f1536ae9837 100644
--- a/platforms/kernel.in
+++ b/platforms/kernel.in
@@ -252,18 +252,18 @@ comment "Development features"
 
 config KERNEL_EXTRA_MAKEVARS
 	string
-	default "CONFIG_DEBUG_SECTION_MISMATCH=y"
+	default ""
 	prompt "Additional kbuild options"
 	help
 	  Specify extra parameters for the kernel build system here. Useful
 	  options include:
 
 	  * CONFIG_DEBUG_SECTION_MISMATCH=y
-	  Enable this feature if you want kernel's builsystem to check for
+	  Enable this feature if you want the kernel's buildsystem to check for
 	  section mismatches (__devinit/__devexit, __init/__exit). This
 	  entry is valid for 2.6.25 kernels and above. Previous kernel versions
 	  do this check automatically. Enabling this feature is recommended
-	  for kernel development.
+	  for kernel development only because it changes how code is inlined.
 	  Changing this entry will rebuild the whole kernel.
 
 	  * C=1
-- 
2.1.4


-- 
ptxdist mailing list
ptxdist@pengutronix.de

                 reply	other threads:[~2015-06-09 14:12 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1433859141-16035-1-git-send-email-u.kleine-koenig@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /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