user/sven/linux.git/Makefile, branch v4.14.308

Linux 4.14.308

2023-03-11T15:26:55Z

Link: https://lore.kernel.org/r/20230310133710.926811681@linuxfoundation.org Tested-by: Jon Hunter Link: https://lore.kernel.org/r/20230311092102.206109890@linuxfoundation.org Tested-by: Guenter Roeck Signed-off-by: Greg Kroah-Hartman

kbuild: Port silent mode detection to future gnu make.

2023-03-11T15:26:49Z

commit 4bf73588165ba7d32131a043775557a54b6e1db5 upstream. Port silent mode detection to the future (post make-4.4) versions of gnu make. Makefile contains the following piece of make code to detect if option -s is specified on the command line. ifneq ($(findstring s,$(filter-out --%,$(MAKEFLAGS))),) This code is executed by make at parse time and assumes that MAKEFLAGS does not contain command line variable definitions. Currently if the user defines a=s on the command line, then at build only time MAKEFLAGS contains " -- a=s". However, starting with commit dc2d963989b96161472b2cd38cef5d1f4851ea34 MAKEFLAGS contains command line definitions at both parse time and build time. This '-s' detection code then confuses a command line variable definition which contains letter 's' with option -s. $ # old make $ make net/wireless/ocb.o a=s CALL scripts/checksyscalls.sh DESCEND objtool $ # this a new make which defines makeflags at parse time $ ~/src/gmake/make/l64/make net/wireless/ocb.o a=s $ We can see here that the letter 's' from 'a=s' was confused with -s. This patch checks for presence of -s using a method recommended by the make manual here https://www.gnu.org/software/make/manual/make.html#Testing-Flags. Link: https://lists.gnu.org/archive/html/bug-make/2022-11/msg00190.html Reported-by: Jan Palus Signed-off-by: Dmitry Goncharov Signed-off-by: Masahiro Yamada Signed-off-by: Greg Kroah-Hartman

Linux 4.14.307

2023-02-25T10:50:31Z

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

Linux 4.14.306

2023-02-22T11:46:07Z

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

Linux 4.14.305

2023-02-06T06:46:35Z

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

Linux 4.14.304

2023-01-24T06:05:20Z

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

Linux 4.14.303

2023-01-18T08:26:44Z

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

Linux 4.14.302

2022-12-14T10:26:16Z

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

Linux 4.14.301

2022-12-08T10:16:34Z

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

Linux 4.14.300

2022-11-25T16:36:55Z

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