From: "Américo Wang" <xiyou.wangcong@gmail.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Borislav Petkov <bp@alien8.de>, Sam Ravnborg <sam@ravnborg.org>,
Michal Marek <mmarek@suse.cz>,
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 -v4] kbuild: Add extra gcc checks
Date: Tue, 1 Mar 2011 21:20:50 +0800 [thread overview]
Message-ID: <20110301132050.GA24374@cr0.private> (raw)
In-Reply-To: <201103011235.00389.arnd@arndb.de>
On Tue, Mar 01, 2011 at 12:35:00PM +0100, Arnd Bergmann wrote:
>On Monday 28 February 2011, Borislav Petkov wrote:
>> My intention was not to have multiple levels of warnings because then
>> you have to go and enable the different levels and have to remember
>> which level you used last, etc, etc.
>
>I wasn't suggesting more than two, so the two would have very distinct
>definitions:
>
>W=1: Warnings that we would like to fix all over the tree, patches to
> remove these are always welcome and you can build the entire kernel
> with it. Once they are all fixed, we can make the warnings the default.
>
>W=2: Warnings that we know we don't always want to fix, meant for what
> you describe here -- you build a single file and decide what to
> do based on common sense.
>
Right, this makes sense. Borislav, could you implement this?
Thanks.
next prev parent reply other threads:[~2011-03-01 13:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-21 11:03 [PATCH -v4] kbuild: Add extra gcc checks Borislav Petkov
2011-02-28 18:24 ` Borislav Petkov
2011-02-28 18:38 ` Sam Ravnborg
2011-02-28 21:07 ` Arnd Bergmann
2011-02-28 21:31 ` Borislav Petkov
2011-03-01 11:35 ` Arnd Bergmann
2011-03-01 13:20 ` Américo Wang [this message]
2011-03-01 14:56 ` Borislav Petkov
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=20110301132050.GA24374@cr0.private \
--to=xiyou.wangcong@gmail.com \
--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=mmarek@suse.cz \
--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