13 Jan, 2019
1 commit
-
[ Upstream commit ef7cfd00b2caf6edeb7f169682b64be2d0a798cf ]
For the same reason as commit 25896d073d8a ("x86/build: Fix compiler
support check for CONFIG_RETPOLINE"), you cannot put this $(error ...)
into the parse stage of the top Makefile.Perhaps I'd propose a more sophisticated solution later, but this is
the best I can do for now.Link: https://lkml.org/lkml/2017/12/25/211
Reported-by: Paul Gortmaker
Reported-by: Bernd Edlinger
Reported-by: Qian Cai
Cc: Josh Poimboeuf
Signed-off-by: Masahiro Yamada
Tested-by: Qian Cai
Signed-off-by: Sasha Levin
10 Jan, 2019
1 commit
29 Dec, 2018
1 commit
21 Dec, 2018
1 commit
17 Dec, 2018
1 commit
13 Dec, 2018
1 commit
08 Dec, 2018
2 commits
-
commit 217c3e0196758662aa0429863b09d1c13da1c5d6 upstream.
They are too noisy
Signed-off-by: Stephen Rothwell
Signed-off-by: Linus Torvalds
Signed-off-by: Greg Kroah-Hartman
06 Dec, 2018
1 commit
01 Dec, 2018
2 commits
-
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
Reviewed-and-tested-by: Nick Desaulniers
Signed-off-by: Masahiro Yamada
[nc: Adjust context]
Signed-off-by: Nathan Chancellor
Signed-off-by: Greg Kroah-Hartman
27 Nov, 2018
1 commit
23 Nov, 2018
1 commit
21 Nov, 2018
1 commit
14 Nov, 2018
1 commit
10 Nov, 2018
1 commit
04 Nov, 2018
2 commits
-
[ 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
Signed-off-by: Masahiro Yamada
Signed-off-by: Sasha Levin
20 Oct, 2018
1 commit
18 Oct, 2018
1 commit
13 Oct, 2018
1 commit
10 Oct, 2018
1 commit
04 Oct, 2018
1 commit
29 Sep, 2018
1 commit
26 Sep, 2018
1 commit
20 Sep, 2018
1 commit
15 Sep, 2018
1 commit
10 Sep, 2018
1 commit
05 Sep, 2018
2 commits
-
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
Signed-off-by: Thomas Gleixner
Acked-by: Matt Rickard
Cc: Borislav Petkov
Cc: Jason Vas Dias
Cc: David Woodhouse
Cc: Peter Zijlstra
Cc: Andi Kleen
Cc: stable@vger.kernel.org
Link: https://lkml.kernel.org/r/c76538cd3afbe19c6246c2d1715bc6a60bd63985.1534448381.git.luto@kernel.org
Signed-off-by: Greg Kroah-Hartman
24 Aug, 2018
2 commits
-
[ 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
Signed-off-by: Masahiro Yamada
Acked-by: Uwe Kleine-König
Signed-off-by: Sasha Levin
Signed-off-by: Greg Kroah-Hartman
22 Aug, 2018
1 commit
18 Aug, 2018
2 commits
16 Aug, 2018
1 commit
09 Aug, 2018
1 commit
06 Aug, 2018
1 commit
03 Aug, 2018
1 commit
28 Jul, 2018
1 commit