user/sven/linux.git/Makefile, branch v5.11.12

Linux 5.11.12

2021-04-07T13:02:36Z

Tested-by: Linux Kernel Functional Testing Tested-by: Guenter Roeck Tested-by: Jason Self Tested-by: Shuah Khan Tested-by: Jon Hunter Link: https://lore.kernel.org/r/20210405085034.233917714@linuxfoundation.org Signed-off-by: Greg Kroah-Hartman

Linux 5.11.11

2021-03-30T12:30:31Z

Tested-by: Linux Kernel Functional Testing Tested-by: Guenter Roeck Tested-by: Jason Self Tested-by: Shuah Khan Tested-by: Jon Hunter Link: https://lore.kernel.org/r/20210329075633.135869143@linuxfoundation.org Link: https://lore.kernel.org/r/20210329101343.082590961@linuxfoundation.org Signed-off-by: Greg Kroah-Hartman

kbuild: add image_name to no-sync-config-targets

2021-03-30T12:30:09Z

[ Upstream commit 993bdde94547887faaad4a97f0b0480a6da271c3 ] 'make image_name' needs include/config/auto.conf to show the correct output because KBUILD_IMAGE depends on CONFIG options, but should not attempt to resync the configuration. Signed-off-by: Masahiro Yamada Signed-off-by: Sasha Levin

Linux 5.11.10

2021-03-25T09:13:34Z

Signed-off-by: Greg Kroah-Hartman

Linux 5.11.9

2021-03-24T10:54:19Z

Tested-by: Jon Hunter Tested-by: Linux Kernel Functional Testing Tested-by: Guenter Roeck Tested-by: Jason Self Link: https://lore.kernel.org/r/20210322121929.669628946@linuxfoundation.org Signed-off-by: Greg Kroah-Hartman

kbuild: Fix for empty SUBLEVEL or PATCHLEVEL again

2021-03-24T10:54:07Z

commit 207da4c82ade9a6d59f7e794d737ba0748613fa2 upstream. Commit 78d3bb4483ba ("kbuild: Fix for empty SUBLEVEL or PATCHLEVEL") fixed the build error for empty SUBLEVEL or PATCHLEVEL by prepending a zero. Commit 9b82f13e7ef3 ("kbuild: clamp SUBLEVEL to 255") re-introduced this issue. This time, we cannot take the same approach because we have C code: #define LINUX_VERSION_PATCHLEVEL $(PATCHLEVEL) #define LINUX_VERSION_SUBLEVEL $(SUBLEVEL) Replace empty SUBLEVEL/PATCHLEVEL with a zero. Fixes: 9b82f13e7ef3 ("kbuild: clamp SUBLEVEL to 255") Reported-by: Christian Zigotzky Signed-off-by: Masahiro Yamada Reviewed-and-tested-by: Sasha Levin Signed-off-by: Greg Kroah-Hartman

Linux 5.11.8

2021-03-20T09:51:14Z

Tested-by: Linux Kernel Functional Testing Tested-by: Jason Self Tested-by: Guenter Roeck Link: https://lore.kernel.org/r/20210319121747.203523570@linuxfoundation.org Signed-off-by: Greg Kroah-Hartman

Linux 5.11.7

2021-03-17T16:11:47Z

Tested-by: Jon Hunter Tested-by: Jason Self Tested-by: Linux Kernel Functional Testing Tested-by: Guenter Roeck Tested-by: Ross Schmidt Link: https://lore.kernel.org/r/20210315135507.611436477@linuxfoundation.org Signed-off-by: Greg Kroah-Hartman

kbuild: clamp SUBLEVEL to 255

2021-03-17T16:11:32Z

[ Upstream commit 9b82f13e7ef316cdc0a8858f1349f4defce3f9e0 ] 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 Signed-off-by: Masahiro Yamada Signed-off-by: Sasha Levin

Linux 5.11.6

2021-03-11T13:19:18Z

Tested-by: Shuah Khan Tested-by: Guenter Roeck Tested-by: Jason Self Tested-by: Linux Kernel Functional Testing Tested-by: Ross Schmidt Tested-by: Jon Hunter Link: https://lore.kernel.org/r/20210310132320.510840709@linuxfoundation.org Signed-off-by: Greg Kroah-Hartman