summaryrefslogtreecommitdiff
path: root/Makefile
AgeCommit message (Collapse)AuthorFilesLines
2018-12-21Linux 4.14.90v4.14.90Greg Kroah-Hartman1-1/+1
2018-12-17Linux 4.14.89v4.14.89Greg Kroah-Hartman1-1/+1
2018-12-13Linux 4.14.88v4.14.88Greg Kroah-Hartman1-1/+1
2018-12-08Linux 4.14.87v4.14.87Greg Kroah-Hartman1-1/+1
2018-12-08disable stringop truncation warnings for nowStephen Rothwell1-0/+3
commit 217c3e0196758662aa0429863b09d1c13da1c5d6 upstream. They are too noisy Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2018-12-05Linux 4.14.86v4.14.86Greg Kroah-Hartman1-1/+1
2018-12-01Linux 4.14.85v4.14.85Greg Kroah-Hartman1-1/+1
2018-12-01kbuild: allow to use GCC toolchain not in Clang search pathStefan Agner1-3/+5
commit ef8c4ed9db80261f397f0c0bf723684601ae3b52 upstream. When using a GCC cross toolchain which is not in a compiled in Clang search path, Clang reverts to the system assembler and linker. This leads to assembler or linker errors, depending on which tool is first used for a given architecture. It seems that Clang is not searching $PATH for a matching assembler or linker. Make sure that Clang picks up the correct assembler or linker by passing the cross compilers bin directory as search path. This allows to use Clang provided by distributions with GCC toolchains not in /usr/bin. Link: https://github.com/ClangBuiltLinux/linux/issues/78 Signed-off-by: Stefan Agner <stefan@agner.ch> Reviewed-and-tested-by: Nick Desaulniers <ndesaulniers@google.com> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com> [nc: Adjust context] Signed-off-by: Nathan Chancellor <natechancellor@gmail.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2018-11-27Linux 4.14.84v4.14.84Greg Kroah-Hartman1-1/+1
2018-11-23Linux 4.14.83v4.14.83Greg Kroah-Hartman1-1/+1
2018-11-21Linux 4.14.82v4.14.82Greg Kroah-Hartman1-1/+1
2018-11-13Linux 4.14.81v4.14.81Greg Kroah-Hartman1-1/+1
2018-11-10Linux 4.14.80v4.14.80Greg Kroah-Hartman1-1/+1
2018-11-04Linux 4.14.79v4.14.79Greg Kroah-Hartman1-1/+1
2018-11-04kbuild: set no-integrated-as before incl. arch MakefileStefan Agner1-2/+2
[ Upstream commit 0f0e8de334c54c38818a4a5390a39aa09deff5bf ] In order to make sure compiler flag detection for ARM works correctly the no-integrated-as flags need to be set before including the arch specific Makefile. Fixes: cfe17c9bbe6a ("kbuild: move cc-option and cc-disable-warning after incl. arch Makefile") Signed-off-by: Stefan Agner <stefan@agner.ch> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com> Signed-off-by: Sasha Levin <sashal@kernel.org>
2018-10-20Linux 4.14.78v4.14.78Greg Kroah-Hartman1-1/+1
2018-10-18Linux 4.14.77v4.14.77Greg Kroah-Hartman1-1/+1
2018-10-13Linux 4.14.76v4.14.76Greg Kroah-Hartman1-1/+1
2018-10-10Linux 4.14.75v4.14.75Greg Kroah-Hartman1-1/+1
2018-10-04Linux 4.14.74v4.14.74Greg Kroah-Hartman1-1/+1
2018-09-29Linux 4.14.73v4.14.73Greg Kroah-Hartman1-1/+1
2018-09-26Linux 4.14.72v4.14.72Greg Kroah-Hartman1-1/+1
2018-09-19Linux 4.14.71v4.14.71Greg Kroah-Hartman1-1/+1
2018-09-15Linux 4.14.70v4.14.70Greg Kroah-Hartman1-1/+1
2018-09-09Linux 4.14.69v4.14.69Greg Kroah-Hartman1-1/+1
2018-09-05Linux 4.14.68v4.14.68Greg Kroah-Hartman1-1/+1
2018-09-05x86/vdso: Fix vDSO build if a retpoline is emittedAndy Lutomirski1-0/+4
commit 2e549b2ee0e358bc758480e716b881f9cabedb6a upstream. Currently, if the vDSO ends up containing an indirect branch or call, GCC will emit the "external thunk" style of retpoline, and it will fail to link. Fix it by building the vDSO with inline retpoline thunks. I haven't seen any reports of this triggering on an unpatched kernel. Fixes: commit 76b043848fd2 ("x86/retpoline: Add initial retpoline support") Signed-off-by: Andy Lutomirski <luto@kernel.org> Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Acked-by: Matt Rickard <matt@softrans.com.au> Cc: Borislav Petkov <bp@alien8.de> Cc: Jason Vas Dias <jason.vas.dias@gmail.com> Cc: David Woodhouse <dwmw2@infradead.org> Cc: Peter Zijlstra <peterz@infradead.org> Cc: Andi Kleen <ak@linux.intel.com> Cc: stable@vger.kernel.org Link: https://lkml.kernel.org/r/c76538cd3afbe19c6246c2d1715bc6a60bd63985.1534448381.git.luto@kernel.org Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2018-08-24Linux 4.14.67v4.14.67Greg Kroah-Hartman1-1/+1
2018-08-24kbuild: suppress warnings from 'getconf LFS_*'Masahiro Yamada1-3/+3
[ Upstream commit 6d79a7b424a5630a6fcab31fd7c38af4ea9c9a0f ] Suppress warnings for systems that do not recognize LFS_*. getconf: no such configuration parameter `LFS_CFLAGS' getconf: no such configuration parameter `LFS_LDFLAGS' getconf: no such configuration parameter `LFS_LIBS' Fixes: d7f14c66c273 ("kbuild: Enable Large File Support for hostprogs") Reported-by: Chen Feng <puck.chen@hisilicon.com> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com> Acked-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de> Signed-off-by: Sasha Levin <alexander.levin@microsoft.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2018-08-22Linux 4.14.66v4.14.66Greg Kroah-Hartman1-1/+1
2018-08-18Linux 4.14.65v4.14.65Greg Kroah-Hartman1-1/+1
2018-08-17Linux 4.14.64v4.14.64Greg Kroah-Hartman1-1/+1
2018-08-15Linux 4.14.63v4.14.63Greg Kroah-Hartman1-1/+1
2018-08-09Linux 4.14.62v4.14.62Greg Kroah-Hartman1-1/+1
2018-08-06Linux 4.14.61v4.14.61Greg Kroah-Hartman1-1/+1
2018-08-03Linux 4.14.60v4.14.60Greg Kroah-Hartman1-1/+1
2018-07-28Linux 4.14.59v4.14.59Greg Kroah-Hartman1-1/+1
2018-07-28turn off -Wattribute-aliasArnd Bergmann1-0/+1
Starting with gcc-8.1, we get a warning about all system call definitions, which use an alias between functions with incompatible prototypes, e.g.: In file included from ../mm/process_vm_access.c:19: ../include/linux/syscalls.h:211:18: warning: 'sys_process_vm_readv' alias between functions of incompatible types 'long int(pid_t, const struct iovec *, long unsigned int, const struct iovec *, long unsigned int, long unsigned int)' {aka 'long int(int, const struct iovec *, long unsigned int, const struct iovec *, long unsigned int, long unsigned int)'} and 'long int(long int, long int, long int, long int, long int, long int)' [-Wattribute-alias] asmlinkage long sys##name(__MAP(x,__SC_DECL,__VA_ARGS__)) \ ^~~ ../include/linux/syscalls.h:207:2: note: in expansion of macro '__SYSCALL_DEFINEx' __SYSCALL_DEFINEx(x, sname, __VA_ARGS__) ^~~~~~~~~~~~~~~~~ ../include/linux/syscalls.h:201:36: note: in expansion of macro 'SYSCALL_DEFINEx' #define SYSCALL_DEFINE6(name, ...) SYSCALL_DEFINEx(6, _##name, __VA_ARGS__) ^~~~~~~~~~~~~~~ ../mm/process_vm_access.c:300:1: note: in expansion of macro 'SYSCALL_DEFINE6' SYSCALL_DEFINE6(process_vm_readv, pid_t, pid, const struct iovec __user *, lvec, ^~~~~~~~~~~~~~~ ../include/linux/syscalls.h:215:18: note: aliased declaration here asmlinkage long SyS##name(__MAP(x,__SC_LONG,__VA_ARGS__)) \ ^~~ ../include/linux/syscalls.h:207:2: note: in expansion of macro '__SYSCALL_DEFINEx' __SYSCALL_DEFINEx(x, sname, __VA_ARGS__) ^~~~~~~~~~~~~~~~~ ../include/linux/syscalls.h:201:36: note: in expansion of macro 'SYSCALL_DEFINEx' #define SYSCALL_DEFINE6(name, ...) SYSCALL_DEFINEx(6, _##name, __VA_ARGS__) ^~~~~~~~~~~~~~~ ../mm/process_vm_access.c:300:1: note: in expansion of macro 'SYSCALL_DEFINE6' SYSCALL_DEFINE6(process_vm_readv, pid_t, pid, const struct iovec __user *, lvec, This is really noisy and does not indicate a real problem. In the latest mainline kernel, this was addressed by commit bee20031772a ("disable -Wattribute-alias warning for SYSCALL_DEFINEx()"), which seems too invasive to backport. This takes a much simpler approach and just disables the warning across the kernel. Signed-off-by: Arnd Bergmann <arnd@arndb.de> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2018-07-25Linux 4.14.58v4.14.58Greg Kroah-Hartman1-1/+1
2018-07-22Linux 4.14.57v4.14.57Greg Kroah-Hartman1-1/+1
2018-07-17Linux 4.14.56v4.14.56Greg Kroah-Hartman1-1/+1
2018-07-11Linux 4.14.55v4.14.55Greg Kroah-Hartman1-1/+1
2018-07-08Linux 4.14.54v4.14.54Greg Kroah-Hartman1-1/+1
2018-07-03Linux 4.14.53v4.14.53Greg Kroah-Hartman1-1/+1
2018-06-26Linux 4.14.52v4.14.52Greg Kroah-Hartman1-1/+1
2018-06-20Linux 4.14.51v4.14.51Greg Kroah-Hartman1-1/+1
2018-06-16Linux 4.14.50v4.14.50Greg Kroah-Hartman1-1/+1
2018-06-11Linux 4.14.49v4.14.49Greg Kroah-Hartman1-1/+1
2018-06-05Linux 4.14.48v4.14.48Greg Kroah-Hartman1-1/+1
2018-06-05kbuild: clang: disable unused variable warnings only when constantSodagudi Prasad1-2/+1
commit 0a5f41767444cc3b4fc5573921ab914b4f78baaa upstream. Currently, GCC disables -Wunused-const-variable, but not -Wunused-variable, so warns unused variables if they are non-constant. While, Clang does not warn unused variables at all regardless of the const qualifier because -Wno-unused-const-variable is implied by the stronger option -Wno-unused-variable. Disable -Wunused-const-variable instead of -Wunused-variable so that GCC and Clang work in the same way. Signed-off-by: Prasad Sodagudi <psodagud@codeaurora.org> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com> Cc: Guenter Roeck <linux@roeck-us.net> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
generated by cgit v1.2.3 (git 2.39.0) at 2024-10-15 14:27:53 +0300