From: Samuel Martin <s.martin49@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/2] linux-header: bump default to version 4.11
Date: Mon, 1 May 2017 11:16:22 +0200 [thread overview]
Message-ID: <20170501091622.1930-2-s.martin49@gmail.com> (raw)
In-Reply-To: <20170501091622.1930-1-s.martin49@gmail.com>
Signed-off-by: Samuel Martin <s.martin49@gmail.com>
---
changes v1 -> v2:
- add missing BR2_TOOLCHAIN_HEADERS_AT_LEAST_4_11 symbol (ThomasP)
---
| 11 ++++++++++-
toolchain/toolchain-common.in | 4 ++++
2 files changed, 14 insertions(+), 1 deletion(-)
--git a/package/linux-headers/Config.in.host b/package/linux-headers/Config.in.host
index 5c67626b2..b1ef3d623 100644
--- a/package/linux-headers/Config.in.host
+++ b/package/linux-headers/Config.in.host
@@ -6,7 +6,7 @@ config BR2_PACKAGE_HOST_LINUX_HEADERS
choice
prompt "Kernel Headers"
default BR2_KERNEL_HEADERS_AS_KERNEL if BR2_LINUX_KERNEL
- default BR2_KERNEL_HEADERS_4_10
+ default BR2_KERNEL_HEADERS_4_11
help
Select the kernel version to get headers from.
@@ -62,6 +62,10 @@ 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_VERSION
bool "Manually specified Linux version"
@@ -83,6 +87,10 @@ choice
This is used to hide/show some packages that have strict
requirements on the version of kernel headers.
+config BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_11
+ bool "4.11.x"
+ select BR2_TOOLCHAIN_HEADERS_AT_LEAST_4_11
+
config BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_10
bool "4.10.x"
select BR2_TOOLCHAIN_HEADERS_AT_LEAST_4_10
@@ -222,4 +230,5 @@ config BR2_DEFAULT_KERNEL_HEADERS
default "4.4.64" if BR2_KERNEL_HEADERS_4_4
default "4.9.25" if BR2_KERNEL_HEADERS_4_9
default "4.10.13" if BR2_KERNEL_HEADERS_4_10
+ default "4.11" if BR2_KERNEL_HEADERS_4_11
default BR2_DEFAULT_KERNEL_VERSION if BR2_KERNEL_HEADERS_VERSION
diff --git a/toolchain/toolchain-common.in b/toolchain/toolchain-common.in
index 379006d02..c47482455 100644
--- a/toolchain/toolchain-common.in
+++ b/toolchain/toolchain-common.in
@@ -247,6 +247,10 @@ config BR2_TOOLCHAIN_HEADERS_AT_LEAST_4_10
bool
select BR2_TOOLCHAIN_HEADERS_AT_LEAST_4_9
+config BR2_TOOLCHAIN_HEADERS_AT_LEAST_4_11
+ bool
+ select BR2_TOOLCHAIN_HEADERS_AT_LEAST_4_10
+
# This order guarantees that the highest version is set, as kconfig
# stops affecting a value on the first matching default.
config BR2_TOOLCHAIN_HEADERS_AT_LEAST
--
2.12.2
next prev parent reply other threads:[~2017-05-01 9:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-01 9:16 [Buildroot] [PATCH v2 1/2] board: add stm32f429-disc1 config Samuel Martin
2017-05-01 9:16 ` Samuel Martin [this message]
2017-05-01 9:50 ` [Buildroot] [PATCH v2 2/2] linux-header: bump default to version 4.11 Thomas Petazzoni
2017-05-01 9:49 ` [Buildroot] [PATCH v2 1/2] board: add stm32f429-disc1 config Thomas Petazzoni
2017-05-01 10:19 ` Samuel Martin
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=20170501091622.1930-2-s.martin49@gmail.com \
--to=s.martin49@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox