user/sven/linux.git/Makefile, branch v6.13.10

Linux 6.13.10

2025-04-07T08:09:36Z

Link: https://lore.kernel.org/r/20250403151622.273788569@linuxfoundation.org Tested-by: Salvatore Bonaccorso Tested-by: Pavel Machek (CIP) Tested-by: Peter Schneider Tested-by: Mark Brown Tested-by: Shuah Khan Tested-by: Florian Fainelli Tested-by: Jon Hunter Tested-by: Justin M. Forbes Tested-by: Ron Economos Signed-off-by: Greg Kroah-Hartman

Linux 6.13.9

2025-03-28T21:04:59Z

Link: https://lore.kernel.org/r/20250325122149.058346343@linuxfoundation.org Tested-by: Florian Fainelli Tested-by: Miguel Ojeda Tested-by: Mark Brown Tested-by: Ron Economos Tested-by: Takeshi Ogasawara Tested-by: Jon Hunter Tested-by: Christian Heusel Tested-by: Peter Schneider Signed-off-by: Greg Kroah-Hartman

Linux 6.13.8

2025-03-22T19:56:59Z

Link: https://lore.kernel.org/r/20250319143027.685727358@linuxfoundation.org Tested-by: SeongJae Park Tested-by: Jon Hunter Tested-by: Salvatore Bonaccorso Tested-by: Ron Economos Tested-by: Miguel Ojeda Tested-by: Linux Kernel Functional Testing Tested-by: Mark Brown Tested-by: Luna Jernberg Tested-by: Hardik Garg Tested-by: Florian Fainelli Tested-by: Justin M. Forbes Tested-by: Peter Schneider Tested-by: Takeshi Ogasawara Signed-off-by: Greg Kroah-Hartman

Linux 6.13.7

2025-03-13T12:08:08Z

Link: https://lore.kernel.org/r/20250310170447.729440535@linuxfoundation.org Tested-by: SeongJae Park Tested-by: Florian Fainelli Tested-by: Salvatore Bonaccorso Tested-by: Luna Jernberg Tested-by: Ronald Warsow Tested-by: Ron Economos Tested-by: Jon Hunter Tested-By: Achill Gilgenast Tested-by: Takeshi Ogasawara Tested-by: Mark Brown Tested-by: Linux Kernel Functional Testing Tested-by: Shuah Khan Tested-by: Hardik Garg Link: https://lore.kernel.org/r/20250311144241.070217339@linuxfoundation.org Tested-by: Ronald Warsow Tested-by: Jon Hunter Tested-by: Florian Fainelli Tested-by: Miguel Ojeda Tested-by: Peter Schneider Tested-by: Luna Jernberg Tested-by: Linux Kernel Functional Testing Tested-by: Takeshi Ogasawara Tested-by: Mark Brown Tested-by: Justin M. Forbes Tested-by: Hardik Garg Signed-off-by: Greg Kroah-Hartman

kbuild: userprogs: use correct lld when linking through clang

2025-03-13T12:08:03Z

commit dfc1b168a8c4b376fa222b27b97c2c4ad4b786e1 upstream. The userprog infrastructure links objects files through $(CC). Either explicitly by manually calling $(CC) on multiple object files or implicitly by directly compiling a source file to an executable. The documentation at Documentation/kbuild/llvm.rst indicates that ld.lld would be used for linking if LLVM=1 is specified. However clang instead will use either a globally installed cross linker from $PATH called ${target}-ld or fall back to the system linker, which probably does not support crosslinking. For the normal kernel build this is not an issue because the linker is always executed directly, without the compiler being involved. Explicitly pass --ld-path to clang so $(LD) is respected. As clang 13.0.1 is required to build the kernel, this option is available. Fixes: 7f3a59db274c ("kbuild: add infrastructure to build userspace programs") Cc: stable@vger.kernel.org # needs wrapping in $(cc-option) for < 6.9 Signed-off-by: Thomas Weißschuh Reviewed-by: Nathan Chancellor Signed-off-by: Masahiro Yamada Signed-off-by: Greg Kroah-Hartman

Linux 6.13.6

2025-03-07T17:27:16Z

Link: https://lore.kernel.org/r/20250305174505.268725418@linuxfoundation.org Tested-by: Ronald Warsow Tested-by: Salvatore Bonaccorso Tested-by: SeongJae Park Tested-by: Peter Schneider Tested-by: Ron Economos Tested-by: Takeshi Ogasawara Tested-by: Shuah Khan Tested-by: Hardik Garg Link: https://lore.kernel.org/r/20250306151416.469067667@linuxfoundation.org Tested-by: Ronald Warsow Tested-by: Mark Brown Tested-by: Florian Fainelli Tested-by: Peter Schneider Tested-by: Jon Hunter Tested-By: Achill Gilgenast Tested-by: Linux Kernel Functional Testing Tested-by: Takeshi Ogasawara Tested-by: Justin M. Forbes Signed-off-by: Greg Kroah-Hartman

Linux 6.13.5

2025-02-27T12:34:22Z

Link: https://lore.kernel.org/r/20250224142604.442289573@linuxfoundation.org Tested-by: Ronald Warsow Tested-by: FLorian Fainelli Tested-by: Pavel Machek (CIP) Tested-by: Peter Schneider Tested-by: Shuah Khan Tested-by: Ron Economos Link: https://lore.kernel.org/r/20250225064750.953124108@linuxfoundation.org Tested-by: Jon Hunter Tested-by: Takeshi Ogasawara Tested-by: Ronald Warsow Tested-by: Mark Brown Tested-by: Peter Schneider Tested-by: Slade Watkins Tested-by: Florian Fainelli Tested-by: Miguel Ojeda Tested-by: Linux Kernel Functional Testing Tested-By: Achill Gilgenast Tested-by: Luna Jernberg Tested-by: Pavel Machek (CIP) Tested-by: Salvatore Bonaccorso Tested-by: Justin M. Forbes Signed-off-by: Greg Kroah-Hartman

Linux 6.13.4

2025-02-21T13:11:21Z

Link: https://lore.kernel.org/r/20250219082609.533585153@linuxfoundation.org Tested-by: Salvatore Bonaccorso Tested-by: Ronald Warsow Tested-by: Luna Jernberg Tested-by: Peter Schneider Tested-by: Hardik Garg Tested-by: Ron Economos Tested-by: Mark Brown Tested-by: Linux Kernel Functional Testing Tested-by: Ronald Warsow Tested-by: Shuah Khan Link: https://lore.kernel.org/r/20250220104500.178420129@linuxfoundation.org Tested-by: Ronald Warsow Tested-by: Mark Brown Tested-by: Takeshi Ogasawara Tested-by: Hardik Garg Tested-by: Pavel Machek (CIP) Tested-by: Slade Watkins Tested-by: Luna Jernberg Tested-By: Achill Gilgenast Tested-by: Jon Hunter Tested-by: Peter Schneider Signed-off-by: Greg Kroah-Hartman

kbuild: userprogs: fix bitsize and target detection on clang

2025-02-21T13:11:05Z

commit 1b71c2fb04e7a713abc6edde4a412416ff3158f2 upstream. scripts/Makefile.clang was changed in the linked commit to move --target from KBUILD_CFLAGS to KBUILD_CPPFLAGS, as that generally has a broader scope. However that variable is not inspected by the userprogs logic, breaking cross compilation on clang. Use both variables to detect bitsize and target arguments for userprogs. Fixes: feb843a469fb ("kbuild: add $(CLANG_FLAGS) to KBUILD_CPPFLAGS") Cc: stable@vger.kernel.org Signed-off-by: Thomas Weißschuh Reviewed-by: Nathan Chancellor Signed-off-by: Masahiro Yamada Signed-off-by: Greg Kroah-Hartman

tools: fix annoying "mkdir -p ..." logs when building tools in parallel

2025-02-21T13:10:52Z

[ Upstream commit d1d0963121769d8d16150b913fe886e48efefa51 ] When CONFIG_OBJTOOL=y or CONFIG_DEBUG_INFO_BTF=y, parallel builds show awkward "mkdir -p ..." logs. $ make -j16 [ snip ] mkdir -p /home/masahiro/ref/linux/tools/objtool && make O=/home/masahiro/ref/linux subdir=tools/objtool --no-print-directory -C objtool mkdir -p /home/masahiro/ref/linux/tools/bpf/resolve_btfids && make O=/home/masahiro/ref/linux subdir=tools/bpf/resolve_btfids --no-print-directory -C bpf/resolve_btfids Defining MAKEFLAGS= on the command line wipes out command line switches from the resultant MAKEFLAGS definition, even though the command line switches are active. [1] MAKEFLAGS puts all single-letter options into the first word, and that word will be empty if no single-letter options were given. [2] However, this breaks if MAKEFLAGS= is given on the command line. The tools/ and tools/% targets set MAKEFLAGS= on the command line, which breaks the following code in tools/scripts/Makefile.include: short-opts := $(firstword -$(MAKEFLAGS)) If MAKEFLAGS really needs modification, it should be done through the environment variable, as follows: MAKEFLAGS= $(MAKE) ... That said, I question whether modifying MAKEFLAGS is necessary here. The only flag we might want to exclude is --no-print-directory, as the tools build system changes the working directory. However, people might find the "Entering/Leaving directory" logs annoying. I simply removed the offending MAKEFLAGS=. [1]: https://savannah.gnu.org/bugs/?62469 [2]: https://www.gnu.org/software/make/manual/make.html#Testing-Flags Fixes: ea01fa9f63ae ("tools: Connect to the kernel build system") Fixes: a50e43332756 ("perf tools: Honor parallel jobs") Signed-off-by: Masahiro Yamada Tested-by: Daniel Xu Signed-off-by: Sasha Levin