From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/4] Config.in.legacy: add legacy entry for 4.20.x headers
Date: Tue, 18 Jun 2019 13:57:31 +0200 [thread overview]
Message-ID: <20190618115733.28551-2-peter@korsgaard.com> (raw)
In-Reply-To: <20190618115733.28551-1-peter@korsgaard.com>
Commit b3bba8e4254 (package/linux-headers: drop support 4.20 headers)
removed the option for 4.20.x kernel headers, but forgot to add a legacy
option. Add that now.
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
---
Config.in.legacy | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/Config.in.legacy b/Config.in.legacy
index 75d6c723a9..2b8dc3b1ee 100644
--- a/Config.in.legacy
+++ b/Config.in.legacy
@@ -153,6 +153,13 @@ config BR2_GDB_VERSION_8_0
The 8.0.x version of gdb has been removed. Use a newer
version instead.
+config BR2_KERNEL_HEADERS_4_20
+ bool "kernel headers version 4.20.x are no longer supported"
+ select BR2_LEGACY
+ help
+ Version 4.20.x of the Linux kernel headers are no longer
+ maintained upstream and are now removed.
+
comment "Legacy options removed in 2019.05"
config BR2_CSKY_DSP
--
2.11.0
next prev parent reply other threads:[~2019-06-18 11:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-18 11:57 [Buildroot] [PATCH 1/4] {linux, linux-headers}: bump 4.{4, 9, 14, 19}.x / 5.1.x series Peter Korsgaard
2019-06-18 11:57 ` Peter Korsgaard [this message]
2019-06-20 11:28 ` [Buildroot] [PATCH 2/4] Config.in.legacy: add legacy entry for 4.20.x headers Peter Korsgaard
2019-06-18 11:57 ` [Buildroot] [PATCH 3/4] amarula_vyasa_rk3288_defconfig: use same-as-kernel option for kernel headers Peter Korsgaard
2019-06-20 11:28 ` Peter Korsgaard
2019-06-18 11:57 ` [Buildroot] [PATCH 4/4] package/linux-headers: drop support for 5.x headers Peter Korsgaard
2019-06-20 11:28 ` Peter Korsgaard
2019-06-20 11:28 ` [Buildroot] [PATCH 1/4] {linux, linux-headers}: bump 4.{4, 9, 14, 19}.x / 5.1.x series Peter Korsgaard
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=20190618115733.28551-2-peter@korsgaard.com \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/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.