All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Jaswinder Singh Rajput <jaswinder@kernel.org>
Cc: x86 maintainers <x86@kernel.org>, Sam Ravnborg <sam@ravnborg.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [git-pull -tip] Add -Werror to arch/x86/ files only and fix warnings
Date: Wed, 15 Apr 2009 21:37:58 +0200	[thread overview]
Message-ID: <20090415193758.GA32675@elte.hu> (raw)
In-Reply-To: <1239810924.2996.1.camel@ht.satnam>


* Jaswinder Singh Rajput <jaswinder@kernel.org> wrote:

> +config ALLOW_X86_WARNINGS
> +	bool "Continue building x86 despite compiler warnings"
> +	default n
> +	depends on ALLOW_WARNINGS
> +	depends on DEBUG_KERNEL
> +	help
> +	  By enabling this option you will disable -Werror on building
> +	  x86 C files only.

no, it should be something like this:

config ALLOW_X86_WARNINGS
	bool "Continue building x86 despite compiler warnings" if DEBUG_KERNEL
	default y
	help
	  By disabling this option you will enable -Werror builds:
	  i.e. any compiler warning will generate a build 
	  failure. (On arch/x86 files only)

	  Disabe this only if you have a reasonably recent compiler 
	  that does not emit bogus warnings and if you want to help 
	  with fixing warnings. Also choose this if you are an x86 
	  developer trying to make sure that the patches you submit 
	  build warning-free. (The rest of the kernel can emit lots 
	  of build warnings - so your own warnings might be easy to 
	  miss.)

	  Choose Y if unsure.

Note the differences: this will be properly kept 'Y' in most 
situations (allyes, allmod, allno). Also note the explicit 
explanation in the help text.

	Ingo

  reply	other threads:[~2009-04-15 19:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-15 11:04 [git-pull -tip] Add -Werror to arch/x86/ files only and fix warnings Jaswinder Singh Rajput
2009-04-15 11:13 ` Ingo Molnar
2009-04-15 12:25   ` Jaswinder Singh Rajput
2009-04-15 15:55     ` Jaswinder Singh Rajput
2009-04-15 19:37       ` Ingo Molnar [this message]
2009-04-15 19:22 ` Andrew Morton
2009-04-15 19:28   ` Ingo Molnar

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=20090415193758.GA32675@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=jaswinder@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    --cc=x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.