From: Michal Marek <mmarek@suse.cz>
To: behanw@converseincode.com
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
dwmw2@infradead.org, "Jan-Simon Möller" <dl9pf@gmx.de>,
"Mark Charlebois" <charlebm@gmail.com>,
bp@alien8.de
Subject: Re: [PATCH v3] kbuild, LLVMLinux: Supress warnings unless W=1-3
Date: Tue, 05 Aug 2014 15:42:41 +0200 [thread overview]
Message-ID: <53E0DF51.3010506@suse.cz> (raw)
In-Reply-To: <1406866105-24980-1-git-send-email-behanw@converseincode.com>
On 2014-08-01 06:08, behanw@converseincode.com wrote:
> From: Behan Webster <behanw@converseincode.com>
>
> clang has more warnings enabled by default. Turn them off unless W is set.
> This patch fixes a logic bug where warnings in clang were disabled when W was set.
>
> Signed-off-by: Behan Webster <behanw@converseincode.com>
> Signed-off-by: Jan-Simon Möller <dl9pf@gmx.de>
> Signed-off-by: Mark Charlebois <charlebm@gmail.com>
> Cc: mmarek@suse.cz
> Cc: bp@alien8.de
> ---
> Makefile | 1 +
> scripts/Makefile.extrawarn | 22 ++++++++++++----------
> 2 files changed, 13 insertions(+), 10 deletions(-)
OK, this looks better, I applied the patch to kbuild.git#kbuild.
> +KBUILD_CFLAGS += $(call cc-disable-warning, unknown-warning-option)
Do we have -W... options in the Makefiles that clang does not understand
and that are added unconditionally?
Thanks,
Michal
prev parent reply other threads:[~2014-08-05 13:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-16 13:07 3d3d6b847420 ("kbuild: LLVMLinux: Adapt warnings for compilation with clang") Borislav Petkov
2014-06-16 15:29 ` PaX Team
2014-06-16 15:48 ` Jan-Simon Möller
2014-06-29 20:13 ` Borislav Petkov
2014-07-01 0:42 ` [PATCH] kbuild, LLVMLinux: only use warnings when using clang behanw
2014-07-01 10:12 ` Borislav Petkov
2014-07-30 13:04 ` Michal Marek
2014-07-30 21:39 ` Behan Webster
2014-07-31 4:16 ` [PATCH v2] kbuild, LLVMLinux: Supress warnings unless W=1-3 behanw
2014-07-31 8:18 ` Michal Marek
2014-07-31 16:12 ` Behan Webster
2014-07-31 20:46 ` Michal Marek
2014-08-01 4:07 ` Behan Webster
2014-08-01 4:08 ` [PATCH v3] " behanw
2014-08-05 13:42 ` 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=53E0DF51.3010506@suse.cz \
--to=mmarek@suse.cz \
--cc=behanw@converseincode.com \
--cc=bp@alien8.de \
--cc=charlebm@gmail.com \
--cc=dl9pf@gmx.de \
--cc=dwmw2@infradead.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).