From: Fabio Estevam <festevam@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/5] configs/imx6-sabresd: Bump to kernel 4.14
Date: Sun, 12 Nov 2017 20:47:09 -0200 [thread overview]
Message-ID: <1510526830-8044-4-git-send-email-festevam@gmail.com> (raw)
In-Reply-To: <1510526830-8044-1-git-send-email-festevam@gmail.com>
Signed-off-by: Fabio Estevam <festevam@gmail.com>
---
configs/imx6-sabresd_defconfig | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/configs/imx6-sabresd_defconfig b/configs/imx6-sabresd_defconfig
index 18dfe27..5b2b014 100644
--- a/configs/imx6-sabresd_defconfig
+++ b/configs/imx6-sabresd_defconfig
@@ -4,8 +4,8 @@ BR2_ARM_ENABLE_NEON=y
BR2_ARM_ENABLE_VFP=y
BR2_ARM_FPU_VFPV3=y
-# Linux headers same as kernel, a 4.13 series
-BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_13=y
+# Linux headers same as kernel, a 4.14 series
+BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_14=y
# System
BR2_TARGET_GENERIC_GETTY_PORT="ttymxc0"
@@ -32,7 +32,7 @@ BR2_TARGET_UBOOT_SPL_NAME="SPL"
# Kernel
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_CUSTOM_VERSION=y
-BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="4.13.3"
+BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="4.14"
BR2_LINUX_KERNEL_DEFCONFIG="imx_v6_v7"
BR2_LINUX_KERNEL_DTS_SUPPORT=y
BR2_LINUX_KERNEL_INTREE_DTS_NAME="imx6q-sabresd imx6dl-sabresd imx6qp-sabresd"
--
2.7.4
next prev parent reply other threads:[~2017-11-12 22:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-12 22:47 [Buildroot] [PATCH 1/5] toolchain: add 4.14.x choice for headers Fabio Estevam
2017-11-12 22:47 ` [Buildroot] [PATCH 2/5] linux-headers: bump to 4.14 kernel version Fabio Estevam
2017-11-12 22:47 ` [Buildroot] [PATCH 3/5] linux: bump default to version 4.14 Fabio Estevam
2017-11-12 22:47 ` Fabio Estevam [this message]
2017-11-12 22:47 ` [Buildroot] [PATCH 5/5] configs/imx6-sabresd_qt5: Bump to kernel 4.14 Fabio Estevam
2017-11-13 22:22 ` [Buildroot] [PATCH 1/5] toolchain: add 4.14.x choice for headers 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=1510526830-8044-4-git-send-email-festevam@gmail.com \
--to=festevam@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