summaryrefslogtreecommitdiff
path: root/Makefile
AgeCommit message (Collapse)Author
2016-09-02Linux 4.1.32v4.1.32Sasha Levin
Signed-off-by: Sasha Levin <alexander.levin@verizon.com>
2016-08-22Linux 4.1.31v4.1.31Sasha Levin
Signed-off-by: Sasha Levin <alexander.levin@verizon.com>
2016-08-08Linux 4.1.30v4.1.30Sasha Levin
Signed-off-by: Sasha Levin <alexander.levin@verizon.com>
2016-07-29Linux 4.1.29v4.1.29Sasha Levin
Signed-off-by: Sasha Levin <alexander.levin@verizon.com>
2016-07-13Linux 4.1.28v4.1.28Sasha Levin
Signed-off-by: Sasha Levin <sasha.levin@oracle.com>
2016-06-22Linux 4.1.27v4.1.27Sasha Levin
Signed-off-by: Sasha Levin <sasha.levin@oracle.com>
2016-06-06Linux 4.1.26v4.1.26Sasha Levin
Signed-off-by: Sasha Levin <sasha.levin@oracle.com>
2016-06-06kbuild: move -Wunused-const-variable to W=1 warning levelArnd Bergmann
[ Upstream commit c9c6837d39311b0cc14cdbe7c18e815ab44aefb1 ] gcc-6 started warning by default about variables that are not used anywhere and that are marked 'const', generating many false positives in an allmodconfig build, e.g.: arch/arm/mach-davinci/board-da830-evm.c:282:20: warning: 'da830_evm_emif25_pins' defined but not used [-Wunused-const-variable=] arch/arm/plat-omap/dmtimer.c:958:34: warning: 'omap_timer_match' defined but not used [-Wunused-const-variable=] drivers/bluetooth/hci_bcm.c:625:39: warning: 'acpi_bcm_default_gpios' defined but not used [-Wunused-const-variable=] drivers/char/hw_random/omap-rng.c:92:18: warning: 'reg_map_omap4' defined but not used [-Wunused-const-variable=] drivers/devfreq/exynos/exynos5_bus.c:381:32: warning: 'exynos5_busfreq_int_pm' defined but not used [-Wunused-const-variable=] drivers/dma/mv_xor.c:1139:34: warning: 'mv_xor_dt_ids' defined but not used [-Wunused-const-variable=] This is similar to the existing -Wunused-but-set-variable warning that was added in an earlier release and that we disable by default now and only enable when W=1 is set, so it makes sense to do the same here. Once we have eliminated the majority of the warnings for both, we can put them back into the default list. We probably want this in backport kernels as well, to allow building them with gcc-6 without introducing extra warnings. Signed-off-by: Arnd Bergmann <arnd@arndb.de> Acked-by: Olof Johansson <olof@lixom.net> Acked-by: Lee Jones <lee.jones@linaro.org> Cc: stable@vger.kernel.org Signed-off-by: Michal Marek <mmarek@suse.com> Signed-off-by: Sasha Levin <sasha.levin@oracle.com>
2016-06-06gcov: disable tree-loop-im to reduce stack usageArnd Bergmann
[ Upstream commit c87bf431448b404a6ef5fbabd74c0e3e42157a7f ] Enabling CONFIG_GCOV_PROFILE_ALL produces us a lot of warnings like lib/lz4/lz4hc_compress.c: In function 'lz4_compresshcctx': lib/lz4/lz4hc_compress.c:514:1: warning: the frame size of 1504 bytes is larger than 1024 bytes [-Wframe-larger-than=] After some investigation, I found that this behavior started with gcc-4.9, and opened https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69702. A suggested workaround for it is to use the -fno-tree-loop-im flag that turns off one of the optimization stages in gcc, so the code runs a little slower but does not use excessive amounts of stack. We could make this conditional on the gcc version, but I could not find an easy way to do this in Kbuild and the benefit would be fairly small, given that most of the gcc version in production are affected now. I'm marking this for 'stable' backports because it addresses a bug with code generation in gcc that exists in all kernel versions with the affected gcc releases. Signed-off-by: Arnd Bergmann <arnd@arndb.de> Acked-by: Peter Oberparleiter <oberpar@linux.vnet.ibm.com> Cc: stable@vger.kernel.org Signed-off-by: Michal Marek <mmarek@suse.com> Signed-off-by: Sasha Levin <sasha.levin@oracle.com>
2016-05-20Linux 4.1.25v4.1.25Sasha Levin
Signed-off-by: Sasha Levin <sasha.levin@oracle.com>
2016-05-11Linux 4.1.24v4.1.24Sasha Levin
Signed-off-by: Sasha Levin <sasha.levin@oracle.com>
2016-04-25Linux 4.1.23v4.1.23Sasha Levin
Signed-off-by: Sasha Levin <sasha.levin@oracle.com>
2016-04-19Linux 4.1.22v4.1.22Sasha Levin
Signed-off-by: Sasha Levin <sasha.levin@oracle.com>
2016-04-03Linux 4.1.21v4.1.21Sasha Levin
Signed-off-by: Sasha Levin <sasha.levin@oracle.com>
2016-03-17Linux 4.1.20v4.1.20Sasha Levin
Signed-off-by: Sasha Levin <sasha.levin@oracle.com>
2016-03-04Linux 4.1.19v4.1.19Sasha Levin
Signed-off-by: Sasha Levin <sasha.levin@oracle.com>
2016-02-15Linux 4.1.18v4.1.18Sasha Levin
Signed-off-by: Sasha Levin <sasha.levin@oracle.com>
2016-01-31Linux 4.1.17v4.1.17Greg Kroah-Hartman
2016-01-22Linux 4.1.16v4.1.16Greg Kroah-Hartman
2015-12-14Linux 4.1.15v4.1.15Greg Kroah-Hartman
2015-12-09Linux 4.1.14v4.1.14Greg Kroah-Hartman
2015-11-09Linux 4.1.13v4.1.13Greg Kroah-Hartman
2015-10-27Linux 4.1.12v4.1.12Greg Kroah-Hartman
2015-10-22Linux 4.1.11v4.1.11Greg Kroah-Hartman
2015-10-03Linux 4.1.10v4.1.10Greg Kroah-Hartman
2015-09-29Linux 4.1.9v4.1.9Greg Kroah-Hartman
2015-09-21Linux 4.1.8v4.1.8Greg Kroah-Hartman
2015-09-13Linux 4.1.7v4.1.7Greg Kroah-Hartman
2015-08-16Linux 4.1.6v4.1.6Greg Kroah-Hartman
2015-08-10Linux 4.1.5v4.1.5Greg Kroah-Hartman
2015-08-10kbuild: Allow arch Makefiles to override {cpp,ld,c}flagsMichal Marek
commit 61754c18752ffb78145671e94f053fb202fff041 upstream. Since commit a1c48bb1 (Makefile: Fix unrecognized cross-compiler command line options), the arch Makefile is included earlier by the main Makefile, preventing the arc architecture to set its -O3 compiler option. Since there might be more use cases for an arch Makefile to fine-tune the options, add support for ARCH_CPPFLAGS, ARCH_AFLAGS and ARCH_CFLAGS variables that are appended to the respective kbuild variables. The user still has the final say via the KCPPFLAGS, KAFLAGS and KCFLAGS variables. Reported-by: Vineet Gupta <Vineet.Gupta1@synopsys.com> Signed-off-by: Michal Marek <mmarek@suse.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2015-08-03Linux 4.1.4v4.1.4Greg Kroah-Hartman
2015-07-21Linux 4.1.3v4.1.3Greg Kroah-Hartman
2015-07-10Linux 4.1.2v4.1.2Greg Kroah-Hartman
2015-06-29Linux 4.1.1v4.1.1Greg Kroah-Hartman
2015-06-21Linux 4.1v4.1Linus Torvalds
2015-06-14Linux 4.1-rc8v4.1-rc8Linus Torvalds
2015-06-07Linux 4.1-rc7v4.1-rc7Linus Torvalds
2015-05-31Linux 4.1-rc6v4.1-rc6Linus Torvalds
2015-05-24Linux 4.1-rc5v4.1-rc5Linus Torvalds
2015-05-18Linux 4.1-rc4v4.1-rc4Linus Torvalds
2015-05-10Linux 4.1-rc3v4.1-rc3Linus Torvalds
2015-05-03Linux 4.1-rc2v4.1-rc2Linus Torvalds
2015-04-26Linux 4.1-rc1v4.1-rc1Linus Torvalds
2015-04-15Merge branch 'kbuild' of ↵Linus Torvalds
git://git.kernel.org/pub/scm/linux/kernel/git/mmarek/kbuild Pull kbuild updates from Michal Marek: "Here is the first round of kbuild changes for v4.1-rc1: - kallsyms fix for ARM and cleanup - make dep(end) removed (developers have no sense of nostalgia these days...) - include Makefiles by relative path - stop useless rebuilds of asm-offsets.h and bounds.h" * 'kbuild' of git://git.kernel.org/pub/scm/linux/kernel/git/mmarek/kbuild: Kbuild: kallsyms: drop special handling of pre-3.0 GCC symbols Kbuild: kallsyms: ignore veneers emitted by the ARM linker kbuild: ia64: use $(src)/Makefile.gate rather than particular path kbuild: include $(src)/Makefile rather than $(obj)/Makefile kbuild: use relative path more to include Makefile kbuild: use relative path to include Makefile kbuild: do not add $(bounds-file) and $(offsets-file) to targets kbuild: remove warning about "make depend" kbuild: Don't reset timestamps in include/generated if not needed
2015-04-13Merge branch 'locking-core-for-linus' of ↵Linus Torvalds
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip Pull core locking changes from Ingo Molnar: "Main changes: - jump label asm preparatory work for PowerPC (Anton Blanchard) - rwsem optimizations and cleanups (Davidlohr Bueso) - mutex optimizations and cleanups (Jason Low) - futex fix (Oleg Nesterov) - remove broken atomicity checks from {READ,WRITE}_ONCE() (Peter Zijlstra)" * 'locking-core-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip: powerpc, jump_label: Include linux/jump_label.h to get HAVE_JUMP_LABEL define jump_label: Allow jump labels to be used in assembly jump_label: Allow asm/jump_label.h to be included in assembly locking/mutex: Further simplify mutex_spin_on_owner() locking: Remove atomicy checks from {READ,WRITE}_ONCE locking/rtmutex: Rename argument in the rt_mutex_adjust_prio_chain() documentation as well locking/rwsem: Fix lock optimistic spinning when owner is not running locking: Remove ACCESS_ONCE() usage locking/rwsem: Check for active lock before bailing on spinning locking/rwsem: Avoid deceiving lock spinners locking/rwsem: Set lock ownership ASAP locking/rwsem: Document barrier need when waking tasks locking/futex: Check PF_KTHREAD rather than !p->mm to filter out kthreads locking/mutex: Refactor mutex_spin_on_owner() locking/mutex: In mutex_spin_on_owner(), return true when owner changes
2015-04-12Linux 4.0v4.0Linus Torvalds
2015-04-09jump_label: Allow jump labels to be used in assemblyAnton Blanchard
To use jump labels in assembly we need the HAVE_JUMP_LABEL define, so we select a fallback version if the toolchain does not support them. Modify linux/jump_label.h so it can be included by assembly files. We also need to add -DCC_HAVE_ASM_GOTO to KBUILD_AFLAGS. Signed-off-by: Anton Blanchard <anton@samba.org> Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org> Cc: Andrew Morton <akpm@linux-foundation.org> Cc: Linus Torvalds <torvalds@linux-foundation.org> Cc: Paul E. McKenney <paulmck@linux.vnet.ibm.com> Cc: Peter Zijlstra <peterz@infradead.org> Cc: Thomas Gleixner <tglx@linutronix.de> Cc: benh@kernel.crashing.org Cc: catalin.marinas@arm.com Cc: davem@davemloft.net Cc: heiko.carstens@de.ibm.com Cc: jbaron@akamai.com Cc: linux@arm.linux.org.uk Cc: linuxppc-dev@lists.ozlabs.org Cc: liuj97@gmail.com Cc: mgorman@suse.de Cc: mmarek@suse.cz Cc: mpe@ellerman.id.au Cc: paulus@samba.org Cc: ralf@linux-mips.org Cc: rostedt@goodmis.org Cc: schwidefsky@de.ibm.com Cc: will.deacon@arm.com Link: http://lkml.kernel.org/r/1428551492-21977-2-git-send-email-anton@samba.org Signed-off-by: Ingo Molnar <mingo@kernel.org>
2015-04-06Linux 4.0-rc7v4.0-rc7Linus Torvalds
2015-04-02kbuild: use relative path more to include MakefileMasahiro Yamada
Prior to this commit, it was impossible to use relative path to include Makefiles from the top level Makefile because the option "--include-dir=$(srctree)" becomes effective when Make enters into sub Makefiles. To use relative path in any places, this commit moves the option above the "sub-make" target. Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com> Signed-off-by: Michal Marek <mmarek@suse.cz>
generated by cgit v1.2.3 (git 2.0.4) at 2024-05-28 18:07:05 +0000