summaryrefslogtreecommitdiffstats
path: root/Makefile
diff options
context:
space:
mode:
authorLuc Van Oostenryck <luc.vanoostenryck@gmail.com>2018-02-15 22:07:50 +0100
committerMasahiro Yamada <yamada.masahiro@socionext.com>2018-03-02 00:26:46 +0900
commit6c49f359ca14f973970324afc9b20208fa0bbad5 (patch)
tree8d72a5a0d225594d4cf762a7507e961db5205ca0 /Makefile
parent61277981dd535ee4b5947b6069badb16f3a21ace (diff)
downloadlinux-stable-6c49f359ca14f973970324afc9b20208fa0bbad5.tar.gz
linux-stable-6c49f359ca14f973970324afc9b20208fa0bbad5.tar.bz2
linux-stable-6c49f359ca14f973970324afc9b20208fa0bbad5.zip
kbuild: disable sparse warnings about unknown attributes
Currently, sparse issues warnings on code using an attribute it doesn't know about. One of the problem with this is that these warnings have no value for the developer, it's just noise for him. At best these warnings tell something about some deficiencies of sparse itself but not about a potential problem with code analyzed. A second problem with this is that sparse release are, alas, less frequent than new attributes are added to GCC. So, avoid the noise by asking sparse to not warn about attributes it doesn't know about. Reference: https://marc.info/?l=linux-sparse&m=151871600016790 Reference: https://marc.info/?l=linux-sparse&m=151871725417322 Signed-off-by: Luc Van Oostenryck <luc.vanoostenryck@gmail.com> Acked-by: Randy Dunlap <rdunlap@infradead.org> Tested-by: Randy Dunlap <rdunlap@infradead.org> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Diffstat (limited to 'Makefile')
-rw-r--r--Makefile2
1 files changed, 1 insertions, 1 deletions
diff --git a/Makefile b/Makefile
index ae07c704ba6f..7b3080423b8a 100644
--- a/Makefile
+++ b/Makefile
@@ -388,7 +388,7 @@ PYTHON = python
CHECK = sparse
CHECKFLAGS := -D__linux__ -Dlinux -D__STDC__ -Dunix -D__unix__ \
- -Wbitwise -Wno-return-void $(CF)
+ -Wbitwise -Wno-return-void -Wno-unknown-attribute $(CF)
NOSTDINC_FLAGS =
CFLAGS_MODULE =
AFLAGS_MODULE =