From: Michal Marek <mmarek@suse.cz>
To: Borislav Petkov <bp@alien8.de>, Arnd Bergmann <arnd@arndb.de>,
Sam Ravnborg <sam@ravnborg.org>,
torvalds@linux-foundation.org, x86@kernel.org,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
linux-kbuild@vger.kernel.org, bp@amd64.org
Subject: Re: [PATCH -v5] kbuild: Add extra gcc checks
Date: Wed, 9 Mar 2011 15:45:04 +0100 [thread overview]
Message-ID: <20110309144504.GA1096@sepie.suse.cz> (raw)
In-Reply-To: <20110301083529.GA767@liondog.tnic>
On Tue, Mar 01, 2011 at 09:35:29AM +0100, Borislav Petkov wrote:
> Add a 'W=1' Makefile switch which adds additional checking per build
> object.
>
> The idea behind this option is targeted at developers who, in the
> process of writing their code, want to do the occasional
>
> make W=1 [target.o]
>
> and let gcc do more extensive code checking for them. Then, they
> could eyeball the output for valid gcc warnings about various
> bugs/discrepancies which are not reported during the normal build
> process.
>
> For more background information and a use case, read through this
> thread: http://marc.info/?l=kernel-janitors&m=129802065918147&w=2
>
> -v5: Document internal kbuild variable which is introduced by this.
> Simplify assignment.
Thanks, applied to kbuild-2.6.git#packaging. If someone comes up with a
good selection of warnings for W=1 and W=2, we can change it later.
Michal
next prev parent reply other threads:[~2011-03-09 14:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-01 8:35 [PATCH -v5] kbuild: Add extra gcc checks Borislav Petkov
2011-03-09 14:45 ` Michal Marek [this message]
2011-03-09 15:06 ` Borislav Petkov
2011-03-09 15:11 ` Ingo Molnar
2011-03-09 17:56 ` Sam Ravnborg
2011-03-10 9:04 ` Ingo Molnar
2011-03-10 9:17 ` Michal Marek
2011-03-10 10:25 ` Sam Ravnborg
2011-03-10 9:20 ` Borislav Petkov
2011-03-10 11:56 ` Arnd Bergmann
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=20110309144504.GA1096@sepie.suse.cz \
--to=mmarek@suse.cz \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=bp@amd64.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sam@ravnborg.org \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox