From: Michal Marek <mmarek@suse.cz>
To: Paul Bolle <pebolle@tiscali.nl>,
Jonathan Toppins <jtoppins@cumulusnetworks.com>
Cc: linux-kbuild@vger.kernel.org
Subject: Re: [PATCH v1 kbuild for-next 1/2] makefiles: add config option to force all cc warnings to errors
Date: Wed, 18 Mar 2015 09:32:18 +0100 [thread overview]
Message-ID: <55093812.6030300@suse.cz> (raw)
In-Reply-To: <1426633120.15575.17.camel@x220>
On 2015-03-17 23:58, Paul Bolle wrote:
> Feel free to fix as many build warning as you can. I'd really appreciate
> that. But my x86_64 build of v4.0-rc4 is _almost_ warning free. And
> that's nice. And I find -Werror (and littering Makefiles with
> cc-disable-warning) just to remove the few warnings I still see plain
> silly. I'm sure the same holds for other people and their builds too.
In addition to what Paul wrote, to review and fix warnings, it's IMO
much more practical to grep the build logs than have the build stop at
the first warning encountered.
Michal
prev parent reply other threads:[~2015-03-18 8:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-17 22:37 [PATCH v1 kbuild for-next 1/2] makefiles: add config option to force all cc warnings to errors Jonathan Toppins
2015-03-17 22:37 ` [PATCH v1 kbuild for-next 2/2] modpost: add Kconfig option to report warnings as errors Jonathan Toppins
2015-03-17 22:58 ` [PATCH v1 kbuild for-next 1/2] makefiles: add config option to force all cc warnings to errors Paul Bolle
2015-03-17 23:15 ` Jonathan Toppins
2015-03-18 10:00 ` Paul Bolle
2015-03-18 2:05 ` Jonathan Toppins
2015-03-18 10:16 ` Paul Bolle
2015-03-18 8:32 ` Michal Marek [this message]
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=55093812.6030300@suse.cz \
--to=mmarek@suse.cz \
--cc=jtoppins@cumulusnetworks.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=pebolle@tiscali.nl \
/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.