From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@buildroot.org
Subject: [Buildroot] [PATCH 1/2] package/linux-headers: drop 5.13.x headers
Date: Wed, 3 Nov 2021 22:40:10 +0100 [thread overview]
Message-ID: <20211103214012.26524-1-peter@korsgaard.com> (raw)
The 5.13.x series is now EOL, so drop it.
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
---
Config.in.legacy | 7 +++++++
linux/linux.hash | 1 -
| 5 -----
3 files changed, 7 insertions(+), 6 deletions(-)
diff --git a/Config.in.legacy b/Config.in.legacy
index 23c3ee29ee..9e0a41574a 100644
--- a/Config.in.legacy
+++ b/Config.in.legacy
@@ -213,6 +213,13 @@ config BR2_KERNEL_HEADERS_5_12
Version 5.12.x of the Linux kernel headers are no longer
maintained upstream and are now removed.
+config BR2_KERNEL_HEADERS_5_13
+ bool "kernel headers version 5.13.x are no longer supported"
+ select BR2_LEGACY
+ help
+ Version 5.13.x of the Linux kernel headers are no longer
+ maintained upstream and are now removed.
+
comment "Legacy options removed in 2021.08"
config BR2_TARGET_GRUB2_BUILTIN_MODULES
diff --git a/linux/linux.hash b/linux/linux.hash
index e58f25ae3c..32fe47d096 100644
--- a/linux/linux.hash
+++ b/linux/linux.hash
@@ -1,7 +1,6 @@
# From https://www.kernel.org/pub/linux/kernel/v5.x/sha256sums.asc
sha256 57b2cf6991910e3b67a1b3490022e8a0674b6965c74c12da1e99d138d1991ee8 linux-5.15.tar.xz
sha256 4dff4e96d4052195002538027f8a810411ba6116a41bff5575952702d509d06a linux-5.14.14.tar.xz
-sha256 e877ec724e917c967603225c7e5dc21b6e0f34998c7d086cab8c50324363ab7b linux-5.13.19.tar.xz
sha256 0a2b2f5fefb90773190aaef4726ac363e03992aedc424b0a57eca092d084304b linux-5.10.75.tar.xz
sha256 cc0c0f902748d251cb22d0e69e3b8d260c447eb0072ef853da15da6cce775038 linux-5.4.155.tar.xz
# From https://www.kernel.org/pub/linux/kernel/v4.x/sha256sums.asc
--git a/package/linux-headers/Config.in.host b/package/linux-headers/Config.in.host
index 12d2caa20a..3a25667ea0 100644
--- a/package/linux-headers/Config.in.host
+++ b/package/linux-headers/Config.in.host
@@ -58,10 +58,6 @@ config BR2_KERNEL_HEADERS_5_10
bool "Linux 5.10.x kernel headers"
select BR2_TOOLCHAIN_HEADERS_AT_LEAST_5_10
-config BR2_KERNEL_HEADERS_5_13
- bool "Linux 5.13.x kernel headers"
- select BR2_TOOLCHAIN_HEADERS_AT_LEAST_5_13
-
config BR2_KERNEL_HEADERS_5_14
bool "Linux 5.14.x kernel headers"
select BR2_TOOLCHAIN_HEADERS_AT_LEAST_5_14
@@ -384,7 +380,6 @@ config BR2_DEFAULT_KERNEL_HEADERS
default "4.19.213" if BR2_KERNEL_HEADERS_4_19
default "5.4.155" if BR2_KERNEL_HEADERS_5_4
default "5.10.75" if BR2_KERNEL_HEADERS_5_10
- default "5.13.19" if BR2_KERNEL_HEADERS_5_13
default "5.14.14" if BR2_KERNEL_HEADERS_5_14
default "5.15" if BR2_KERNEL_HEADERS_5_15
default BR2_DEFAULT_KERNEL_VERSION if BR2_KERNEL_HEADERS_VERSION
--
2.20.1
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2021-11-03 21:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-03 21:40 Peter Korsgaard [this message]
2021-11-03 21:40 ` [Buildroot] [PATCH 2/2] {linux, linux-headers}: bump 4.{4, 9, 14, 19}.x / 5.{4, 10, 14}.x series Peter Korsgaard
2021-11-04 12:06 ` Peter Korsgaard
2021-11-03 21:57 ` [Buildroot] [PATCH 1/2] package/linux-headers: drop 5.13.x headers Thomas Petazzoni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211103214012.26524-1-peter@korsgaard.com \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.