linux-headers: bump 4.{4, 9, 14, 17, 18}.x series
PATCH 1/3 linux-headers: bump 4.{4, 9, 14, 17, 18}.x series
--- package/linux-headers/Config.in.host | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-)
package/linux-headers/Config.in.host +5 -5
@@ -266,15 +266,15 @@ config BR2_DEFAULT_KERNEL_HEADERS string default "3.2.102" if BR2_KERNEL_HEADERS_3_2 default "4.1.52" if BR2_KERNEL_HEADERS_4_1 - default "4.4.145" if BR2_KERNEL_HEADERS_4_4 - default "4.9.116" if BR2_KERNEL_HEADERS_4_9 + default "4.4.152" if BR2_KERNEL_HEADERS_4_4 + default "4.9.124" if BR2_KERNEL_HEADERS_4_9 default "4.10.17" if BR2_KERNEL_HEADERS_4_10 default "4.11.12" if BR2_KERNEL_HEADERS_4_11 default "4.12.14" if BR2_KERNEL_HEADERS_4_12 default "4.13.16" if BR2_KERNEL_HEADERS_4_13 - default "4.14.59" if BR2_KERNEL_HEADERS_4_14 + default "4.14.67" if BR2_KERNEL_HEADERS_4_14 default "4.15.18" if BR2_KERNEL_HEADERS_4_15 default "4.16.18" if BR2_KERNEL_HEADERS_4_16 - default "4.17.11" if BR2_KERNEL_HEADERS_4_17 - default "4.18.3" if BR2_KERNEL_HEADERS_4_18 + default "4.17.19" if BR2_KERNEL_HEADERS_4_17 + default "4.18.5" if BR2_KERNEL_HEADERS_4_18 default BR2_DEFAULT_KERNEL_VERSION if BR2_KERNEL_HEADERS_VERSION
Signature · 1 line
2.18.0
PATCH 2/3 linux: bump default to version 4.18.5
--- linux/Config.in | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
linux/Config.in +1 -1
@@ -120,7 +120,7 @@ endif config BR2_LINUX_KERNEL_VERSION string - default "4.18.4" if BR2_LINUX_KERNEL_LATEST_VERSION + default "4.18.5" if BR2_LINUX_KERNEL_LATEST_VERSION default "v4.4.130-cip23" if BR2_LINUX_KERNEL_LATEST_CIP_VERSION default BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE \ if BR2_LINUX_KERNEL_CUSTOM_VERSION
Signature · 1 line
2.18.0
Thomas Petazzoni
AppliedPATCH 2/3 linux: bump default to version 4.18.5
Hello,
Quoted 4 lines · Bernd Kuhls
Signed-off-by Bernd Kuhls <[email protected]>--- linux/Config.in | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Applied to next, thanks.
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons) Embedded Linux and Kernel engineering https://bootlin.com
PATCH 3/3 linux-headers: drop old unsupported 4.x versions
In reply to Bernd KuhlsThese versions received their last updated more than three months ago and are no longer supported according to
https://www.kernel.org/category/releases.html, so drop them and add legacy entries.
--- Config.in.legacy | 53 ++++++++++++++++++++++++++++ package/linux-headers/Config.in.host | 25 ------------- 2 files changed, 53 insertions(+), 25 deletions(-)
Config.in.legacy +53 -0
@@ -142,6 +142,59 @@ comment "unpredictable ways. " comment "----------------------------------------------------" endif +############################################################################### +comment "Legacy options removed in 2018.11" + +config BR2_KERNEL_HEADERS_4_10 + bool "kernel headers version 4.10.x are no longer supported" + select BR2_KERNEL_HEADERS_4_14 + select BR2_LEGACY + help + Version 4.10.x of the Linux kernel headers are no longer + maintained upstream and are now removed. As an alternative, + version 4.14.x of the headers have been automatically + selected in your configuration. + +config BR2_KERNEL_HEADERS_4_11 + bool "kernel headers version 4.11.x are no longer supported" + select BR2_KERNEL_HEADERS_4_14 + select BR2_LEGACY + help + Version 4.11.x of the Linux kernel headers are no longer + maintained upstream and are now removed. As an alternative, + version 4.14.x of the headers have been automatically + selected in your configuration. + +config BR2_KERNEL_HEADERS_4_12 + bool "kernel headers version 4.12.x are no longer supported" + select BR2_KERNEL_HEADERS_4_14 + select BR2_LEGACY + help + Version 4.12.x of the Linux kernel headers are no longer + maintained upstream and are now removed. As an alternative, + version 4.14.x of the headers have been automatically + selected in your configuration. + +config BR2_KERNEL_HEADERS_4_13 + bool "kernel headers version 4.13.x are no longer supported" + select BR2_KERNEL_HEADERS_4_14 + select BR2_LEGACY + help + Version 4.13.x of the Linux kernel headers are no longer + maintained upstream and are now removed. As an alternative, + version 4.14.x of the headers have been automatically + selected in your configuration. + +config BR2_KERNEL_HEADERS_4_15 + bool "kernel headers version 4.15.x are no longer supported" + select BR2_KERNEL_HEADERS_4_14 + select BR2_LEGACY + help + Version 4.15.x of the Linux kernel headers are no longer + maintained upstream and are now removed. As an alternative, + version 4.14.x of the headers have been automatically + selected in your configuration. + ############################################################################### comment "Legacy options removed in 2018.08"
package/linux-headers/Config.in.host +0 -25
@@ -43,30 +43,10 @@ config BR2_KERNEL_HEADERS_4_9 bool "Linux 4.9.x kernel headers" select BR2_TOOLCHAIN_HEADERS_AT_LEAST_4_9 -config BR2_KERNEL_HEADERS_4_10 - bool "Linux 4.10.x kernel headers" - select BR2_TOOLCHAIN_HEADERS_AT_LEAST_4_10 - -config BR2_KERNEL_HEADERS_4_11 - bool "Linux 4.11.x kernel headers" - select BR2_TOOLCHAIN_HEADERS_AT_LEAST_4_11 - -config BR2_KERNEL_HEADERS_4_12 - bool "Linux 4.12.x kernel headers" - select BR2_TOOLCHAIN_HEADERS_AT_LEAST_4_12 - -config BR2_KERNEL_HEADERS_4_13 - bool "Linux 4.13.x kernel headers" - select BR2_TOOLCHAIN_HEADERS_AT_LEAST_4_13 - config BR2_KERNEL_HEADERS_4_14 bool "Linux 4.14.x kernel headers" select BR2_TOOLCHAIN_HEADERS_AT_LEAST_4_14 -config BR2_KERNEL_HEADERS_4_15 - bool "Linux 4.15.x kernel headers" - select BR2_TOOLCHAIN_HEADERS_AT_LEAST_4_15 - config BR2_KERNEL_HEADERS_4_16 bool "Linux 4.16.x kernel headers" select BR2_TOOLCHAIN_HEADERS_AT_LEAST_4_16
@@ -268,12 +248,7 @@ config BR2_DEFAULT_KERNEL_HEADERS default "4.1.52" if BR2_KERNEL_HEADERS_4_1 default "4.4.152" if BR2_KERNEL_HEADERS_4_4 default "4.9.124" if BR2_KERNEL_HEADERS_4_9 - default "4.10.17" if BR2_KERNEL_HEADERS_4_10 - default "4.11.12" if BR2_KERNEL_HEADERS_4_11 - default "4.12.14" if BR2_KERNEL_HEADERS_4_12 - default "4.13.16" if BR2_KERNEL_HEADERS_4_13 default "4.14.67" if BR2_KERNEL_HEADERS_4_14 - default "4.15.18" if BR2_KERNEL_HEADERS_4_15 default "4.16.18" if BR2_KERNEL_HEADERS_4_16 default "4.17.19" if BR2_KERNEL_HEADERS_4_17 default "4.18.5" if BR2_KERNEL_HEADERS_4_18
Signature · 1 line
2.18.0
Thomas Petazzoni
AppliedPATCH 3/3 linux-headers: drop old unsupported 4.x versions
Hello,
Quoted 16 lines · Bernd Kuhls
These versions received their last updated more than three months ago and are no longer supported according to
https://www.kernel.org/category/releases.html, so drop them and add legacy entries.Signed-off-by Bernd Kuhls <[email protected]>--- Config.in.legacy | 53 ++++++++++++++++++++++++++++ package/linux-headers/Config.in.host | 25 ------------- 2 files changed, 53 insertions(+), 25 deletions(-)Config.in.legacy +0
-0
Config.in.legacy comment "unpredictable ways. " · line 150
Quoted 9 lines
Config.in.legacy +6
-0@@ -142,6 +142,59 @@ comment "unpredictable ways. " comment "----------------------------------------------------" endif +############################################################################### +comment "Legacy options removed in 2018.11" + +config BR2_KERNEL_HEADERS_4_10 + bool "kernel headers version 4.10.x are no longer supported" + select BR2_KERNEL_HEADERS_4_14
I think it makes more sense to automatically select some *older* kernel headers. Indeed, if the user was using 4.10 kernel headers, presumably he is using some 4.10/4.11/4.12 kernel, so if we upgrade the kernel headers to 4.14... the new build may not work at runtime, the kernel headers being more recent than the running kernel.
So instead for 4.10, 4.11, 4.12 and 4.13, I've changed to select the 4.9 kernel headers instead.
Applied to next with this change.
Thanks!
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
PATCH 3/3 linux-headers: drop old unsupported 4.x versions
Am Fri, 24 Aug 2018 23:02:33 +0200 schrieb Thomas Petazzoni:
Quoted 5 lines
I think it makes more sense to automatically select some *older* kernel headers. Indeed, if the user was using 4.10 kernel headers, presumably he is using some 4.10/4.11/4.12 kernel, so if we upgrade the kernel headers to 4.14... the new build may not work at runtime, the kernel headers being more recent than the running kernel.
Hi Thomas,
when preparing this patch I searched for previous removals of kernel versions for orientation on how to handle the legacy options and found this patch/commit by Peter where he upgraded the versions:
https://git.buildroot.net/buildroot/commit/?
id=2a9b7b8a1ec0f200c6b82641512325284dee9a54
Regards, Bernd
PATCH 3/3 linux-headers: drop old unsupported 4.x versions
Quoted 9 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Bernd" == Bernd Kuhls <[email protected]> writes:
Am Fri, 24 Aug 2018 23:02:33 +0200 schrieb Thomas Petazzoni:
Quoted 5 lines
I think it makes more sense to automatically select some *older* kernel headers. Indeed, if the user was using 4.10 kernel headers, presumably he is using some 4.10/4.11/4.12 kernel, so if we upgrade the kernel headers to 4.14... the new build may not work at runtime, the kernel headers being more recent than the running kernel.
Quoted 8 lines
Hi Thomas,
when preparing this patch I searched for previous removals of kernel versions for orientation on how to handle the legacy options and found this patch/commit by Peter where he upgraded the versions:
https://git.buildroot.net/buildroot/commit/?
id=2a9b7b8a1ec0f200c6b82641512325284dee9a54
Hmm, that was a mistake. I must have missed that we still had an entry for 3.2.
Signature · 1 line
Bye, Peter Korsgaard
PATCH 3/3 linux-headers: drop old unsupported 4.x versions
In reply to Thomas PetazzoniThomas, Bernd, All,
On 2018-08-24 23:02 +0200, Thomas Petazzoni spake thusly:
Quoted 22 lines
Hello,
Quoted 19 lines · Bernd Kuhls
These versions received their last updated more than three months ago and are no longer supported according to
https://www.kernel.org/category/releases.html, so drop them and add legacy entries.Signed-off-by Bernd Kuhls <[email protected]>--- Config.in.legacy | 53 ++++++++++++++++++++++++++++ package/linux-headers/Config.in.host | 25 ------------- 2 files changed, 53 insertions(+), 25 deletions(-)Config.in.legacy +0
-0@@ -142,6 +142,59 @@ comment "unpredictable ways. " comment "----------------------------------------------------" endif
Quoted 9 lines
Config.in.legacy comment "unpredictable ways. " · line 150
Quoted 6 lines
Config.in.legacy +6
-0+############################################################################### +comment "Legacy options removed in 2018.11" + +config BR2_KERNEL_HEADERS_4_10 + bool "kernel headers version 4.10.x are no longer supported" + select BR2_KERNEL_HEADERS_4_14I think it makes more sense to automatically select some *older* kernel headers.
Except it is not allowed to select a choice entry anyway.
I'll send a patch removing the selects, since they do not work...
Regards,
Yann E. MORIN.
Signature · 6 lines
.-----------------.--------------------.------------------.--------------------. | Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: | | +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ | | +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no | | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. | '------------------------------^-------^------------------^--------------------'
PATCH 1/3 linux-headers: bump 4.{4, 9, 14, 17, 18}.x series
In reply to Bernd KuhlsHello,
Quoted 20 lines · Bernd Kuhls
Signed-off-by Bernd Kuhls <[email protected]>--- package/linux-headers/Config.in.host | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-)package/linux-headers/Config.in.host +2
-2@@ -266,15 +266,15 @@ config BR2_DEFAULT_KERNEL_HEADERS string default "3.2.102" if BR2_KERNEL_HEADERS_3_2 default "4.1.52" if BR2_KERNEL_HEADERS_4_1 - default "4.4.145" if BR2_KERNEL_HEADERS_4_4 - default "4.9.116" if BR2_KERNEL_HEADERS_4_9 + default "4.4.152" if BR2_KERNEL_HEADERS_4_4 + default "4.9.124" if BR2_KERNEL_HEADERS_4_9 default "4.10.17" if BR2_KERNEL_HEADERS_4_10 default "4.11.12" if BR2_KERNEL_HEADERS_4_11 default "4.12.14" if BR2_KERNEL_HEADERS_4_12
package/linux-headers/Config.in.host config BR2_DEFAULT_KERNEL_HEADERS · line 280
Quoted 10 lines
package/linux-headers/Config.in.host +3
-3default "4.13.16" if BR2_KERNEL_HEADERS_4_13 - default "4.14.59" if BR2_KERNEL_HEADERS_4_14 + default "4.14.67" if BR2_KERNEL_HEADERS_4_14 default "4.15.18" if BR2_KERNEL_HEADERS_4_15 default "4.16.18" if BR2_KERNEL_HEADERS_4_16 - default "4.17.11" if BR2_KERNEL_HEADERS_4_17 - default "4.18.3" if BR2_KERNEL_HEADERS_4_18 + default "4.17.19" if BR2_KERNEL_HEADERS_4_17 + default "4.18.5" if BR2_KERNEL_HEADERS_4_18 default BR2_DEFAULT_KERNEL_VERSION if BR2_KERNEL_HEADERS_VERSION
I've applied to next, but after cherry-picking 59af8a3a223d2d5fdd6496ef59b79be38d957df5 from master, so only the 4.18.5 update remained.
It would be nice if Fabio and you could hold off a bit on Linux 4.18 updates, until next gets merged back into master after 2018.08. Indeed for now, doing all those 4.18 updates is not that important, we will have plenty of time before 2018.11 is released to update to the latest 4.18 (and possibly 4.19) before the release. In general, I don't mind getting those updates regularly, but right now, with the master/next split, it's just causing merge conflicts every time, for no great benefit.
Of course, updates to < 4.18 for master are more than welcome!
Thanks!
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Bootlin Embedded Linux and Kernel engineering https://bootlin.com