Select Git revision
Search by author
- Any Author
- authors
-
Alexander Sterger alexander.sterger
-
Andrii Sosiuk
andrii.sosiuk
-
**** group_556_bot_74cce396359e27efa6278607a72ef350
-
Bernd Mierzowski bernd.mierzowski
-
Christian Stimming
christian.stimming
-
Christoph Kutzera christoph.kutzera
-
Christos Karampeazis
-
CI Variables Management Service Account service_account_ci_vars_management
-
Davide Cardillo
davide.cardillo
-
Dietmar Muscholik dietmar.muscholik
-
Dmitry Petrov dmitry.petrov
-
Felix Gerking felix.gerking
-
GitBot
gitbot
-
Git Bot Service Account
service_account_gitbot
-
Hai Nam Tran hai.nam.tran
-
Hilmar Bode hilmar.bode
-
Jan-Ove Korneffel jan-ove.korneffel
-
Jonas Höppner jonas.hoeppner
-
Lorenzo Pagliai
lorenzo.pagliai
-
Lukas Rosky lukas.rosky
- Mar 20, 2021
-
-
Greg Kroah-Hartman authored
Tested-by:
Florian Fainelli <f.fainelli@gmail.com> Tested-by:
Jason Self <jason@bluehome.net> Tested-by:
Guenter Roeck <linux@roeck-us.net> Tested-by:
Linux Kernel Functional Testing <lkft@linaro.org> Link: https://lore.kernel.org/r/20210319121745.449875976@linuxfoundation.org Signed-off-by:
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
-
- Mar 17, 2021
-
-
Greg Kroah-Hartman authored
Tested-by:
Jon Hunter <jonathanh@nvidia.com> Tested-by:
Hulk Robot <hulkrobot@huawei.com> Tested-by:
Ross Schmidt <ross.schm.dev@gmail.com> Link: https://lore.kernel.org/r/20210315135550.333963635@linuxfoundation.org Signed-off-by:
-
Sasha Levin authored
[ Upstream commit 9b82f13e ] Right now if SUBLEVEL becomes larger than 255 it will overflow into the territory of PATCHLEVEL, causing havoc in userspace that tests for specific kernel version. While userspace code tests for MAJOR and PATCHLEVEL, it doesn't test SUBLEVEL at any point as ABI changes don't happen in the context of stable tree. Thus, to avoid overflows, simply clamp SUBLEVEL to it's maximum value in the context of LINUX_VERSION_CODE. This does not affect "make kernelversion" and such. Signed-off-by:
Sasha Levin <sashal@kernel.org> Signed-off-by:
Masahiro Yamada <masahiroy@kernel.org> Signed-off-by:
-
- Mar 11, 2021
-
-
Greg Kroah-Hartman authored
Tested-by:
Shuah Khan <skhan@linuxfoundation.org> Tested-by:
-
- Mar 09, 2021
-
-
Greg Kroah-Hartman authored
Tested-by:
Hulk Robot <hulkci@huawei.com> Tested-by:
-
- Mar 07, 2021
-
-
Greg Kroah-Hartman authored
Tested-by:
-
- Mar 04, 2021
-
-
Greg Kroah-Hartman authored
Tested-by:
-
- Feb 26, 2021
-
-
Greg Kroah-Hartman authored
Tested-by:
-
- Feb 23, 2021
-
-
Greg Kroah-Hartman authored
Tested-by:
Igor Matheus Andrade Torrente <igormtorrente@gmail.com> Tested-by:
-
- Feb 17, 2021
-
-
Greg Kroah-Hartman authored
Tested-by:
-
- Feb 13, 2021
-
-
Greg Kroah-Hartman authored
Tested-by:
-
- Feb 10, 2021
-
-
Greg Kroah-Hartman authored
Tested-by:
-
Josh Poimboeuf authored
commit 20bf2b37 upstream. With retpolines disabled, some configurations of GCC, and specifically the GCC versions 9 and 10 in Ubuntu will add Intel CET instrumentation to the kernel by default. That breaks certain tracing scenarios by adding a superfluous ENDBR64 instruction before the fentry call, for functions which can be called indirectly. CET instrumentation isn't currently necessary in the kernel, as CET is only supported in user space. Disable it unconditionally and move it into the x86's Makefile as CET/CFI... enablement should be a per-arch decision anyway. [ bp: Massage and extend commit message. ] Fixes: 29be86d7 ("kbuild: add -fcf-protection=none when using retpoline flags") Reported-by:
Nikolay Borisov <nborisov@suse.com> Signed-off-by:
Josh Poimboeuf <jpoimboe@redhat.com> Signed-off-by:
Borislav Petkov <bp@suse.de> Reviewed-by:
-
- Feb 07, 2021
-
-
Greg Kroah-Hartman authored
Tested-by:
-
- Feb 03, 2021
-
-
Greg Kroah-Hartman authored
Tested-by:
-
- Jan 30, 2021
-
-
Greg Kroah-Hartman authored
Link: https://lore.kernel.org/r/20210129105910.132680016@linuxfoundation.org Signed-off-by:
-
- Jan 27, 2021
-
-
Greg Kroah-Hartman authored
Tested-by:
-
- Jan 23, 2021
-
-
Greg Kroah-Hartman authored
Tested-by:
-
- Jan 19, 2021
-
-
Greg Kroah-Hartman authored
Tested-by:
-
Olaf Hering authored
commit 172aad81 upstream. Catch errors which at least gcc tolerates by default: warning: 'return' with no value, in function returning non-void [-Wreturn-type] Signed-off-by:
Olaf Hering <olaf@aepfle.de> Signed-off-by:
-
- Jan 17, 2021
-
-
Greg Kroah-Hartman authored
Tested-by:
-
- Jan 12, 2021
-
-
Greg Kroah-Hartman authored
Tested-by:
-
Dominique Martinet authored
commit 436e980e upstream. depmod is not guaranteed to be in /sbin, just let make look for it in the path like all the other invoked programs Signed-off-by:
Dominique Martinet <asmadeus@codewreck.org> Signed-off-by:
-
- Jan 09, 2021
-
-
Greg Kroah-Hartman authored
Tested-by:
-
- Jan 06, 2021
-
-
Greg Kroah-Hartman authored
Tested-by:
-
- Dec 30, 2020
-
-
Greg Kroah-Hartman authored
Tested-by:
-
- Dec 21, 2020
-
-
Greg Kroah-Hartman authored
Tested-by:
-
- Dec 16, 2020
-
-
Greg Kroah-Hartman authored
Tested-by:
-
Nick Desaulniers authored
commit b8a90923 upstream. Clang's integrated assembler produces the warning for assembly files: warning: DWARF2 only supports one section per compilation unit If -Wa,-gdwarf-* is unspecified, then debug info is not emitted for assembly sources (it is still emitted for C sources). This will be re-enabled for newer DWARF versions in a follow up patch. Enables defconfig+CONFIG_DEBUG_INFO to build cleanly with LLVM=1 LLVM_IAS=1 for x86_64 and arm64. Cc: <stable@vger.kernel.org> Link: https://github.com/ClangBuiltLinux/linux/issues/716 Reported-by:
Dmitry Golovin <dima@golovin.in> Reported-by:
Nathan Chancellor <natechancellor@gmail.com> Suggested-by:
Sedat Dilek <sedat.dilek@gmail.com> Reviewed-by:
Fangrui Song <maskray@google.com> Reviewed-by:
Nick Desaulniers <ndesaulniers@google.com> Signed-off-by:
-
- Dec 11, 2020
-
-
Greg Kroah-Hartman authored
Tested-by:
-
- Dec 08, 2020
-
-
Greg Kroah-Hartman authored
Tested-by:
-
- Dec 02, 2020
-
-
Greg Kroah-Hartman authored
Tested-by:
-
- Nov 24, 2020
-
-
Greg Kroah-Hartman authored
Tested-by:
-
- Nov 22, 2020
-
-
Greg Kroah-Hartman authored
Tested-by:
-
- Nov 18, 2020
-
-
Greg Kroah-Hartman authored
Tested-by:
-
- Nov 10, 2020
-
-
Greg Kroah-Hartman authored
Signed-off-by: -
Greg Kroah-Hartman authored
Tested-by:
-
- Nov 05, 2020
-
-
Greg Kroah-Hartman authored
Tested-by:
-
- Nov 01, 2020
-
-
Greg Kroah-Hartman authored
Tested-by:
-
- Oct 29, 2020
-
-
Greg Kroah-Hartman authored
Tested-by:
-
