All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/4] amarula_vyasa_rk3288_defconfig: use same-as-kernel option for kernel headers
Date: Tue, 18 Jun 2019 13:57:32 +0200	[thread overview]
Message-ID: <20190618115733.28551-3-peter@korsgaard.com> (raw)
In-Reply-To: <20190618115733.28551-1-peter@korsgaard.com>

Instead of the to-be-removed 5.0 option.

Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
---
 configs/amarula_vyasa_rk3288_defconfig | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/configs/amarula_vyasa_rk3288_defconfig b/configs/amarula_vyasa_rk3288_defconfig
index 6fd46b6455..760ad3f9f4 100644
--- a/configs/amarula_vyasa_rk3288_defconfig
+++ b/configs/amarula_vyasa_rk3288_defconfig
@@ -4,7 +4,7 @@ BR2_cortex_a17=y
 BR2_ARM_FPU_NEON_VFPV4=y
 
 # Linux headers same as kernel, a 5.0 series
-BR2_KERNEL_HEADERS_5_0=y
+BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_5_0=y
 
 # Bootloader
 BR2_TARGET_UBOOT=y
-- 
2.11.0

  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 ` [Buildroot] [PATCH 2/4] Config.in.legacy: add legacy entry for 4.20.x headers Peter Korsgaard
2019-06-20 11:28   ` Peter Korsgaard
2019-06-18 11:57 ` Peter Korsgaard [this message]
2019-06-20 11:28   ` [Buildroot] [PATCH 3/4] amarula_vyasa_rk3288_defconfig: use same-as-kernel option for kernel headers 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-3-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.