summaryrefslogtreecommitdiff
path: root/Makefile
AgeCommit message (Collapse)Author
2017-10-05Linux 4.9.53Greg Kroah-Hartman
2017-09-27Linux 4.9.52Greg Kroah-Hartman
2017-09-20Linux 4.9.51Greg Kroah-Hartman
2017-09-13Linux 4.9.50Greg Kroah-Hartman
2017-09-10Linux 4.9.49Greg Kroah-Hartman
2017-09-07Linux 4.9.48Greg Kroah-Hartman
2017-09-02Linux 4.9.47Greg Kroah-Hartman
2017-08-30Linux 4.9.46Greg Kroah-Hartman
2017-08-25Linux 4.9.45Greg Kroah-Hartman
2017-08-16Linux 4.9.44Greg Kroah-Hartman
2017-08-13Linux 4.9.43Greg Kroah-Hartman
2017-08-11Linux 4.9.42Greg Kroah-Hartman
2017-08-07Linux 4.9.41Greg Kroah-Hartman
2017-07-27Linux 4.9.40Greg Kroah-Hartman
2017-07-27disable new gcc-7.1.1 warnings for nowLinus Torvalds
commit bd664f6b3e376a8ef4990f87d08271cc2d01ba9a upstream. I made the mistake of upgrading my desktop to the new Fedora 26 that comes with gcc-7.1.1. There's nothing wrong per se that I've noticed, but I now have 1500 lines of warnings, mostly from the new format-truncation warning triggering all over the tree. We use 'snprintf()' and friends in a lot of places, and often know that the numbers are fairly small (ie a controller index or similar), but gcc doesn't know that, and sees an 'int', and thinks that it could be some huge number. And then complains when our buffers are not able to fit the name for the ten millionth controller. These warnings aren't necessarily bad per se, and we probably want to look through them subsystem by subsystem, but at least during the merge window they just mean that I can't even see if somebody is introducing any *real* problems when I pull. So warnings disabled for now. Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2017-07-214.9.39Greg Kroah-Hartman
2017-07-15Linux 4.9.38Greg Kroah-Hartman
2017-07-12Linux 4.9.37Greg Kroah-Hartman
2017-07-05Linux 4.9.36Greg Kroah-Hartman
2017-06-29Linux 4.9.35Greg Kroah-Hartman
2017-06-29jump label: fix passing kbuild_cflags when checking for asm goto supportGleb Fotengauer-Malinovskiy
commit 7292ae3d5a18fb922be496e6bb687647193569b4 upstream. The latest change of asm goto support check added passing of KBUILD_CFLAGS to compiler. When these flags reference gcc plugins that are not built yet, the check fails. When one runs "make bzImage" followed by "make modules", the kernel is always built with HAVE_JUMP_LABEL disabled, while the modules are built depending on CONFIG_JUMP_LABEL. If HAVE_JUMP_LABEL macro happens to be different, modules are built with undefined references, e.g.: ERROR: "static_key_slow_inc" [net/netfilter/xt_TEE.ko] undefined! ERROR: "static_key_slow_dec" [net/netfilter/xt_TEE.ko] undefined! ERROR: "static_key_slow_dec" [net/netfilter/nft_meta.ko] undefined! ERROR: "static_key_slow_inc" [net/netfilter/nft_meta.ko] undefined! ERROR: "nf_hooks_needed" [net/netfilter/ipvs/ip_vs.ko] undefined! ERROR: "nf_hooks_needed" [net/ipv6/ipv6.ko] undefined! ERROR: "static_key_count" [net/ipv6/ipv6.ko] undefined! ERROR: "static_key_slow_inc" [net/ipv6/ipv6.ko] undefined! This change moves the check before all these references are added to KBUILD_CFLAGS. This is correct because subsequent KBUILD_CFLAGS modifications are not relevant to this check. Reported-by: Anton V. Boyarshinov <boyarsh@altlinux.org> Fixes: 35f860f9ba6a ("jump label: pass kbuild_cflags when checking for asm goto support") Signed-off-by: Gleb Fotengauer-Malinovskiy <glebfm@altlinux.org> Signed-off-by: Dmitry V. Levin <ldv@altlinux.org> Acked-by: Steven Rostedt (VMware) <rostedt@goodmis.org> Acked-by: David Lin <dtwlin@google.com> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2017-06-24Linux 4.9.34Greg Kroah-Hartman
2017-06-17Linux 4.9.33Greg Kroah-Hartman
2017-06-17jump label: pass kbuild_cflags when checking for asm goto supportDavid Lin
[ Upstream commit 35f860f9ba6aac56cc38e8b18916d833a83f1157 ] Some versions of ARM GCC compiler such as Android toolchain throws in a '-fpic' flag by default. This causes the gcc-goto check script to fail although some config would have '-fno-pic' flag in the KBUILD_CFLAGS. This patch passes the KBUILD_CFLAGS to the check script so that the script does not rely on the default config from different compilers. Link: http://lkml.kernel.org/r/20170120234329.78868-1-dtwlin@google.com Signed-off-by: David Lin <dtwlin@google.com> Acked-by: Steven Rostedt <rostedt@goodmis.org> Cc: Michal Marek <mmarek@suse.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> Signed-off-by: Sasha Levin <alexander.levin@verizon.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2017-06-14Linux 4.9.32Greg Kroah-Hartman
2017-06-07Linux 4.9.31Greg Kroah-Hartman
2017-05-25Linux 4.9.30Greg Kroah-Hartman
2017-05-20Linux 4.9.29Greg Kroah-Hartman
2017-05-14Linux 4.9.28Greg Kroah-Hartman
2017-05-08Linux 4.9.27Greg Kroah-Hartman
2017-05-03Linux 4.9.26Greg Kroah-Hartman
2017-04-27Linux 4.9.25Greg Kroah-Hartman
2017-04-21Linux 4.9.24Greg Kroah-Hartman
2017-04-18Linux 4.9.23Greg Kroah-Hartman
2017-04-12Linux 4.9.22Greg Kroah-Hartman
2017-04-12Kbuild: use cc-disable-warning consistently for maybe-uninitializedArnd Bergmann
commit b334e19ae9381f12a7521976883022385d2b7eef upstream. In commit a76bcf557ef4 ("Kbuild: enable -Wmaybe-uninitialized warning for "make W=1""), I reverted another change that happened to fix a problem with old compilers, and now we get this report again with old compilers (prior to gcc-4.8) and GCOV enabled: cc1: warnings being treated as errors drivers/gpu/drm/i915/intel_ringbuffer.c: In function 'intel_ring_setup_status_page': drivers/gpu/drm/i915/intel_ringbuffer.c:438: error: 'mmio.reg' may be used uninitialized in this function At top level: >> cc1: error: unrecognized command line option "-Wno-maybe-uninitialized" The problem is that we turn off the warning conditionally in a number of places as we should, but one of them does it unconditionally. Instead, change it to call cc-disable-warning as we do elsewhere. The original patch that caused it was merged into linux-4.7, then 4.8 removed the change and 4.9 brought it back, so we probably want a backport to 4.9 once this is merged. Use a ':=' assignment instead of '=' to force the cc-disable-warning call to only be evaluated once instead of every time. Fixes: a76bcf557ef4 ("Kbuild: enable -Wmaybe-uninitialized warning for "make W=1"") Fixes: e72e2dfe7c16 ("gcov: disable -Wmaybe-uninitialized warning") Reported-by: kbuild test robot <fengguang.wu@intel.com> Signed-off-by: Arnd Bergmann <arnd@arndb.de> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2017-04-08Linux 4.9.21Greg Kroah-Hartman
2017-03-31Linux 4.9.20Greg Kroah-Hartman
2017-03-30Linux 4.9.19Greg Kroah-Hartman
2017-03-26Linux 4.9.18Greg Kroah-Hartman
2017-03-22Linux 4.9.17Greg Kroah-Hartman
2017-03-18Linux 4.9.16Greg Kroah-Hartman
2017-03-15Linux 4.9.15Greg Kroah-Hartman
2017-03-12Linux 4.9.14Greg Kroah-Hartman
2017-02-26Linux 4.9.13Greg Kroah-Hartman
2017-02-23Linux 4.9.12Greg Kroah-Hartman
2017-02-18Linux 4.9.11Greg Kroah-Hartman
2017-02-14Linux 4.9.10Greg Kroah-Hartman
2017-02-09Linux 4.9.9Greg Kroah-Hartman
2017-02-04Linux 4.9.8Greg Kroah-Hartman