summaryrefslogtreecommitdiff
path: root/Makefile
AgeCommit message (Collapse)AuthorFilesLines
2017-12-16Linux 4.9.70v4.9.70Greg Kroah-Hartman1-1/+1
2017-12-16kbuild: do not call cc-option before KBUILD_CFLAGS initializationMasahiro Yamada1-10/+11
[ Upstream commit 433dc2ebe7d17dd21cba7ad5c362d37323592236 ] Some $(call cc-option,...) are invoked very early, even before KBUILD_CFLAGS, etc. are initialized. The returned string from $(call cc-option,...) depends on KBUILD_CPPFLAGS, KBUILD_CFLAGS, and GCC_PLUGINS_CFLAGS. Since they are exported, they are not empty when the top Makefile is recursively invoked. The recursion occurs in several places. For example, the top Makefile invokes itself for silentoldconfig. "make tinyconfig", "make rpm-pkg" are the cases, too. In those cases, the second call of cc-option from the same line runs a different shell command due to non-pristine KBUILD_CFLAGS. To get the same result all the time, KBUILD_* and GCC_PLUGINS_CFLAGS must be initialized before any call of cc-option. This avoids garbage data in the .cache.mk file. Move all calls of cc-option below the config targets because target compiler flags are unnecessary for Kconfig. Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com> Reviewed-by: Douglas Anderson <dianders@chromium.org> Signed-off-by: Sasha Levin <alexander.levin@verizon.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2017-12-14Linux 4.9.69v4.9.69Greg Kroah-Hartman1-1/+1
2017-12-09Linux 4.9.68v4.9.68Greg Kroah-Hartman1-1/+1
2017-12-05Linux 4.9.67v4.9.67Greg Kroah-Hartman1-1/+1
2017-11-30Linux 4.9.66v4.9.66Greg Kroah-Hartman1-1/+1
2017-11-24Linux 4.9.65v4.9.65Greg Kroah-Hartman1-1/+1
2017-11-21Linux 4.9.64v4.9.64Greg Kroah-Hartman1-1/+1
2017-11-18Linux 4.9.63v4.9.63Greg Kroah-Hartman1-1/+1
2017-11-15Linux 4.9.62v4.9.62Greg Kroah-Hartman1-1/+1
2017-11-08Linux 4.9.61v4.9.61Greg Kroah-Hartman1-1/+1
2017-11-02Linux 4.9.60v4.9.60Greg Kroah-Hartman1-1/+1
2017-10-27Linux 4.9.59v4.9.59Greg Kroah-Hartman1-1/+1
2017-10-21Linux 4.9.58v4.9.58Greg Kroah-Hartman1-1/+1
2017-10-18Linux 4.9.57v4.9.57Greg Kroah-Hartman1-1/+1
2017-10-12Linux 4.9.56v4.9.56Greg Kroah-Hartman1-1/+1
2017-10-12Linux 4.9.55v4.9.55Greg Kroah-Hartman1-1/+1
2017-10-08Linux 4.9.54v4.9.54Greg Kroah-Hartman1-1/+1
2017-10-05Linux 4.9.53v4.9.53Greg Kroah-Hartman1-1/+1
2017-09-27Linux 4.9.52v4.9.52Greg Kroah-Hartman1-1/+1
2017-09-20Linux 4.9.51v4.9.51Greg Kroah-Hartman1-1/+1
2017-09-13Linux 4.9.50v4.9.50Greg Kroah-Hartman1-1/+1
2017-09-10Linux 4.9.49v4.9.49Greg Kroah-Hartman1-1/+1
2017-09-07Linux 4.9.48v4.9.48Greg Kroah-Hartman1-1/+1
2017-09-02Linux 4.9.47v4.9.47Greg Kroah-Hartman1-1/+1
2017-08-30Linux 4.9.46v4.9.46Greg Kroah-Hartman1-1/+1
2017-08-24Linux 4.9.45v4.9.45Greg Kroah-Hartman1-1/+1
2017-08-16Linux 4.9.44v4.9.44Greg Kroah-Hartman1-1/+1
2017-08-12Linux 4.9.43v4.9.43Greg Kroah-Hartman1-1/+1
2017-08-11Linux 4.9.42v4.9.42Greg Kroah-Hartman1-1/+1
2017-08-06Linux 4.9.41v4.9.41Greg Kroah-Hartman1-1/+1
2017-07-27Linux 4.9.40v4.9.40Greg Kroah-Hartman1-1/+1
2017-07-27disable new gcc-7.1.1 warnings for nowLinus Torvalds1-0/+3
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.39v4.9.39Greg Kroah-Hartman1-1/+1
2017-07-15Linux 4.9.38v4.9.38Greg Kroah-Hartman1-1/+1
2017-07-12Linux 4.9.37v4.9.37Greg Kroah-Hartman1-1/+1
2017-07-05Linux 4.9.36v4.9.36Greg Kroah-Hartman1-1/+1
2017-06-29Linux 4.9.35v4.9.35Greg Kroah-Hartman1-1/+1
2017-06-29jump label: fix passing kbuild_cflags when checking for asm goto supportGleb Fotengauer-Malinovskiy1-6/+6
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.34v4.9.34Greg Kroah-Hartman1-1/+1
2017-06-17Linux 4.9.33v4.9.33Greg Kroah-Hartman1-1/+1
2017-06-17jump label: pass kbuild_cflags when checking for asm goto supportDavid Lin1-1/+1
[ 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.32v4.9.32Greg Kroah-Hartman1-1/+1
2017-06-07Linux 4.9.31v4.9.31Greg Kroah-Hartman1-1/+1
2017-05-25Linux 4.9.30v4.9.30Greg Kroah-Hartman1-1/+1
2017-05-20Linux 4.9.29v4.9.29Greg Kroah-Hartman1-1/+1
2017-05-14Linux 4.9.28v4.9.28Greg Kroah-Hartman1-1/+1
2017-05-08Linux 4.9.27v4.9.27Greg Kroah-Hartman1-1/+1
2017-05-03Linux 4.9.26v4.9.26Greg Kroah-Hartman1-1/+1
2017-04-27Linux 4.9.25v4.9.25Greg Kroah-Hartman1-1/+1
generated by cgit v1.2.3 (git 2.25.1) at 2025-09-18 01:05:33 +0000