From: Michal Marek <mmarek@suse.cz>
To: Jonathan Toppins <jtoppins@cumulusnetworks.com>
Cc: linux-kbuild@vger.kernel.org
Subject: Re: [PATCH v2 kbuild for-next 1/2] makefiles: add config option to force all cc warnings to errors
Date: Mon, 30 Mar 2015 15:35:50 +0200 [thread overview]
Message-ID: <55195136.3030804@suse.cz> (raw)
In-Reply-To: <1427478671-16379-1-git-send-email-jtoppins@cumulusnetworks.com>
On 2015-03-27 18:51, Jonathan Toppins wrote:
> Add a Kconfig option to force cc warnings to errors. For new
> development it is recommended this setting be enabled as warnings
> in the code will be quite obvious.
I don't want to add such kconfig option, because it will break
all{mod,yes}config for little gain. And there are warnings like the
preprocessor #warning or the use of a function marked as __deprecated --
these a basically TODOs and there is no point in failing the build. Test
builds can be done with KCFLAGS=-Werror or you can grep build logs.
Michal
prev parent reply other threads:[~2015-03-30 13:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-27 17:51 [PATCH v2 kbuild for-next 1/2] makefiles: add config option to force all cc warnings to errors Jonathan Toppins
2015-03-27 17:51 ` [PATCH v2 kbuild for-next 2/2] modpost: add Kconfig option to report warnings as errors Jonathan Toppins
2015-03-30 13:35 ` 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=55195136.3030804@suse.cz \
--to=mmarek@suse.cz \
--cc=jtoppins@cumulusnetworks.com \
--cc=linux-kbuild@vger.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.