From: Bernd Kuhls <bernd@kuhls.net>
To: buildroot@buildroot.org
Subject: [Buildroot] [PATCH 2/2] package/linux-headers: drop 6.19.x option
Date: Thu, 23 Apr 2026 08:14:02 +0200 [thread overview]
Message-ID: <20260423061402.39498-2-bernd@kuhls.net> (raw)
In-Reply-To: <20260423061402.39498-1-bernd@kuhls.net>
The 6.19.x series is now EOL upstream, so drop the linux-headers
option and add legacy handling for it.
Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
---
Config.in.legacy | 7 +++++++
linux/from-6.17/linux.hash | 1 -
| 1 -
| 5 -----
4 files changed, 7 insertions(+), 7 deletions(-)
delete mode 120000 package/linux-headers/6.19.14
diff --git a/Config.in.legacy b/Config.in.legacy
index af093ff3e1..ead9ceaa08 100644
--- a/Config.in.legacy
+++ b/Config.in.legacy
@@ -146,6 +146,13 @@ endif
comment "Legacy options removed in 2026.05"
+config BR2_KERNEL_HEADERS_6_19
+ bool "kernel headers version 6.19.x are no longer supported"
+ select BR2_LEGACY
+ help
+ Version 6.19.x of the Linux kernel headers are no longer
+ maintained upstream and are now removed.
+
config BR2_PACKAGE_PCRE
bool "pcre removed"
select BR2_LEGACY
diff --git a/linux/from-6.17/linux.hash b/linux/from-6.17/linux.hash
index 928ae172cd..a2e1be9d31 100644
--- a/linux/from-6.17/linux.hash
+++ b/linux/from-6.17/linux.hash
@@ -2,7 +2,6 @@
sha256 b2c935a36d24980e11e59bed3ca558ea6d67619ec0065faa335cdc0b64d887bf linux-7.0.1.tar.xz
# From https://www.kernel.org/pub/linux/kernel/v6.x/sha256sums.asc
-sha256 cde8bf6739be4a0777fedbbba5330b8188c55680c45a922a4dfa289cbec6f185 linux-6.19.14.tar.xz
sha256 c207c557ce58103b4dda30e26da5203f3d8467c6dadc53d709f6d83ae1d1255f linux-6.18.24.tar.xz
# Licenses hashes
diff --git a/package/linux-headers/6.19.14 b/package/linux-headers/6.19.14
deleted file mode 120000
index a4e1d3ec9c..0000000000
--- a/package/linux-headers/6.19.14
+++ /dev/null
@@ -1 +0,0 @@
-../../linux/from-6.17
\ No newline at end of file
--git a/package/linux-headers/Config.in.host b/package/linux-headers/Config.in.host
index 7e38fc161e..0c1a90f920 100644
--- a/package/linux-headers/Config.in.host
+++ b/package/linux-headers/Config.in.host
@@ -52,10 +52,6 @@ config BR2_KERNEL_HEADERS_6_18
bool "Linux 6.18.x kernel headers"
select BR2_TOOLCHAIN_HEADERS_AT_LEAST_6_18
-config BR2_KERNEL_HEADERS_6_19
- bool "Linux 6.19.x kernel headers"
- select BR2_TOOLCHAIN_HEADERS_AT_LEAST_6_19
-
config BR2_KERNEL_HEADERS_7_0
bool "Linux 7.0.x kernel headers"
select BR2_TOOLCHAIN_HEADERS_AT_LEAST_7_0
@@ -478,7 +474,6 @@ config BR2_DEFAULT_KERNEL_HEADERS
default "6.6.135" if BR2_KERNEL_HEADERS_6_6
default "6.12.83" if BR2_KERNEL_HEADERS_6_12
default "6.18.24" if BR2_KERNEL_HEADERS_6_18
- default "6.19.14" if BR2_KERNEL_HEADERS_6_19
default "7.0.1" if BR2_KERNEL_HEADERS_7_0
default BR2_DEFAULT_KERNEL_VERSION if BR2_KERNEL_HEADERS_VERSION
default "custom" if BR2_KERNEL_HEADERS_CUSTOM_TARBALL
--
2.47.3
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-04-23 6:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-23 6:14 [Buildroot] [PATCH 1/2] {linux, linux-headers}: bump 6.{12, 18, 19}.x / 7.0.x series Bernd Kuhls
2026-04-23 6:14 ` Bernd Kuhls [this message]
2026-04-23 19:33 ` Julien Olivain via buildroot
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=20260423061402.39498-2-bernd@kuhls.net \
--to=bernd@kuhls.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox