From: Joel Stanley <joel@jms.id.au>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/3] linux: add support for Linux 5.0
Date: Tue, 19 Mar 2019 10:36:38 +1030 [thread overview]
Message-ID: <20190319000638.6259-4-joel@jms.id.au> (raw)
In-Reply-To: <20190319000638.6259-1-joel@jms.id.au>
This sets 5.0 to be the default, moving from 4.19 which was used instead
of 4.20 for the LTS branch.
Signed-off-by: Joel Stanley <joel@jms.id.au>
---
linux/Config.in | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/linux/Config.in b/linux/Config.in
index 818b94e1c0df..7c647abf57fa 100644
--- a/linux/Config.in
+++ b/linux/Config.in
@@ -30,10 +30,8 @@ config BR2_LINUX_NEEDS_MODULES
choice
prompt "Kernel version"
-# We are intentionally staying at 4.19 for the next Buildroot LTS
-# release (2019.02)
config BR2_LINUX_KERNEL_LATEST_VERSION
- bool "Latest version (4.19)"
+ bool "Latest version (5.0)"
config BR2_LINUX_KERNEL_LATEST_CIP_VERSION
bool "Latest CIP SLTS version (v4.4.171-cip30)"
@@ -123,7 +121,7 @@ endif
config BR2_LINUX_KERNEL_VERSION
string
- default "4.19.25" if BR2_LINUX_KERNEL_LATEST_VERSION
+ default "5.0.2" if BR2_LINUX_KERNEL_LATEST_VERSION
default "v4.4.171-cip30" if BR2_LINUX_KERNEL_LATEST_CIP_VERSION
default BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE \
if BR2_LINUX_KERNEL_CUSTOM_VERSION
--
2.20.1
prev parent reply other threads:[~2019-03-19 0:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-19 0:06 [Buildroot] [PATCH 0/3] Linux kernel 5.0 support Joel Stanley
2019-03-19 0:06 ` [Buildroot] [PATCH 1/3] package/linux-headers: add support for Linux 5.0 kernel headers Joel Stanley
2019-03-19 0:06 ` [Buildroot] [PATCH 2/3] toolchain: Add necessary options to support " Joel Stanley
2019-03-19 21:23 ` Thomas Petazzoni
2019-03-19 0:06 ` Joel Stanley [this message]
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=20190319000638.6259-4-joel@jms.id.au \
--to=joel@jms.id.au \
--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.