public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: jflat@chromium.org
To: linux-kbuild@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, yamada.masahiro@socionext.com,
	michal.lkml@markovi.net, Jon Flatley <jflat@chromium.org>
Subject: [PATCH] kbuild, LLVMLinux: Don't suppress format warnings
Date: Fri,  1 Feb 2019 13:08:53 -0800	[thread overview]
Message-ID: <20190201210853.244043-1-jflat@chromium.org> (raw)

From: Jon Flatley <jflat@chromium.org>

gcc produces format warnings that clang suppresses. To keep behavior
consistent between gcc and clang, don't suppress format warnings in
clang.

Signed-off-by: Jon Flatley <jflat@chromium.org>
---
 scripts/Makefile.extrawarn | 1 -
 1 file changed, 1 deletion(-)

diff --git a/scripts/Makefile.extrawarn b/scripts/Makefile.extrawarn
index 768306add591..94daf4e1fc73 100644
--- a/scripts/Makefile.extrawarn
+++ b/scripts/Makefile.extrawarn
@@ -68,7 +68,6 @@ else
 ifdef CONFIG_CC_IS_CLANG
 KBUILD_CFLAGS += $(call cc-disable-warning, initializer-overrides)
 KBUILD_CFLAGS += $(call cc-disable-warning, unused-value)
-KBUILD_CFLAGS += $(call cc-disable-warning, format)
 KBUILD_CFLAGS += $(call cc-disable-warning, sign-compare)
 KBUILD_CFLAGS += $(call cc-disable-warning, format-zero-length)
 KBUILD_CFLAGS += $(call cc-disable-warning, uninitialized)
-- 
2.20.1.611.gfbb209baf1-goog

             reply	other threads:[~2019-02-01 21:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-01 21:08 jflat [this message]
2019-02-05  8:26 ` [PATCH] kbuild, LLVMLinux: Don't suppress format warnings Masahiro Yamada
2019-02-06 16:45   ` Nathan Chancellor
2019-02-06 17:32     ` Jon Flatley
2019-02-06 17:36       ` Nick Desaulniers
2019-02-06 17:43         ` Nathan Chancellor
2019-02-07  0:24           ` Masahiro Yamada
2019-02-07  0:27             ` Masahiro Yamada
2019-02-07  0:30               ` Nick Desaulniers
2019-02-07  0:37                 ` Nathan Chancellor
2019-02-07  0:40                   ` Nick Desaulniers

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=20190201210853.244043-1-jflat@chromium.org \
    --to=jflat@chromium.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.lkml@markovi.net \
    --cc=yamada.masahiro@socionext.com \
    /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