From: Artem Bityutskiy <dedekind1@gmail.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: MIPS Mailing List <linux-mips@linux-mips.org>,
MTD Maling List <linux-mtd@lists.infradead.org>
Subject: [PATCH 1/2] MIPS: Kbuild: remove -Werror
Date: Fri, 27 Apr 2012 16:48:29 +0300 [thread overview]
Message-ID: <1335534510-12573-1-git-send-email-dedekind1@gmail.com> (raw)
From: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
MIPS build fails with the standard W=1 Kbuild switch with because of the
-Werror gcc switch.
This patch removes the gcc switch to make W=1 work. Mips is the only
architecture I know which does not build with W=1 and this upsets my aiaiai
scripts. And in general, you never know which warnings newer versions of gcc
will start emiting so having -Werror by default is not the best idea.
Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
---
arch/mips/Kbuild | 5 -----
1 files changed, 0 insertions(+), 5 deletions(-)
diff --git a/arch/mips/Kbuild b/arch/mips/Kbuild
index 7dd65cf..0d37730 100644
--- a/arch/mips/Kbuild
+++ b/arch/mips/Kbuild
@@ -1,8 +1,3 @@
-# Fail on warnings - also for files referenced in subdirs
-# -Werror can be disabled for specific files using:
-# CFLAGS_<file.o> := -Wno-error
-subdir-ccflags-y := -Werror
-
# platform specific definitions
include arch/mips/Kbuild.platforms
obj-y := $(platform-y)
--
1.7.9.1
next reply other threads:[~2012-04-27 13:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-27 13:48 Artem Bityutskiy [this message]
2012-04-27 13:48 ` [PATCH 2/2] MIPS: bcm63xx: kbuild: remove -Werror Artem Bityutskiy
2012-05-06 7:06 ` Maciej W. Rozycki
2012-05-06 7:36 ` Artem Bityutskiy
2012-05-21 18:15 ` Ralf Baechle
2012-04-27 17:03 ` [PATCH 1/2] MIPS: Kbuild: " David Daney
2012-05-06 7:04 ` Maciej W. Rozycki
2012-05-06 7:34 ` Artem Bityutskiy
2012-05-06 8:32 ` Maciej W. Rozycki
2012-05-06 8:37 ` Artem Bityutskiy
2012-05-06 9:14 ` Maciej W. Rozycki
2012-05-13 12:08 ` Jonas Gorski
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=1335534510-12573-1-git-send-email-dedekind1@gmail.com \
--to=dedekind1@gmail.com \
--cc=linux-mips@linux-mips.org \
--cc=linux-mtd@lists.infradead.org \
--cc=ralf@linux-mips.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).