Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rafal Susz <rafal.susz@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] configs/s6lx9_microboard_defconfig: purge custom dts boolean
Date: Tue, 13 Mar 2018 19:00:06 +0100	[thread overview]
Message-ID: <20180313180006.5364-2-rafal.susz@gmail.com> (raw)
In-Reply-To: <20180313180006.5364-1-rafal.susz@gmail.com>

Since custom dts files are unconditionally handled *KERNEL_USE_CUSTOM_DTS
is no longer available/needed.

Signed-off-by: Rafal Susz <rafal.susz@gmail.com>
---
 configs/s6lx9_microboard_defconfig | 1 -
 1 file changed, 1 deletion(-)

diff --git a/configs/s6lx9_microboard_defconfig b/configs/s6lx9_microboard_defconfig
index f77c80ba87..97b2d3fe79 100644
--- a/configs/s6lx9_microboard_defconfig
+++ b/configs/s6lx9_microboard_defconfig
@@ -10,5 +10,4 @@ BR2_LINUX_KERNEL_CUSTOM_VERSION=y
 BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="4.4.7"
 BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG=y
 BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE="board/avnet/s6lx9_microboard/lx9_mmu_defconfig"
-BR2_LINUX_KERNEL_USE_CUSTOM_DTS=y
 BR2_LINUX_KERNEL_CUSTOM_DTS_PATH="board/avnet/s6lx9_microboard/lx9_mmu.dts"
-- 
2.16.1

  reply	other threads:[~2018-03-13 18:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-12 21:35 [Buildroot] [PATCH 1/1] package/linux: fix custom dts files handling Rafal Susz
2018-03-13 11:32 ` Rafal Susz
2018-03-13 11:49   ` Baruch Siach
2018-03-13 12:31     ` Rafał Susz
2018-03-13 12:45       ` Baruch Siach
2018-03-13 14:26   ` Rafal Susz
2018-03-13 17:21     ` Yann E. MORIN
2018-03-13 18:00     ` [Buildroot] [PATCH 1/2] " Rafal Susz
2018-03-13 18:00       ` Rafal Susz [this message]
2018-03-31 20:59         ` [Buildroot] [PATCH 2/2] configs/s6lx9_microboard_defconfig: purge custom dts boolean Peter Korsgaard
2018-03-14 15:20       ` [Buildroot] [PATCH 1/2] package/linux: fix custom dts files handling Jan Kundrát
2018-03-31 20:59       ` 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=20180313180006.5364-2-rafal.susz@gmail.com \
    --to=rafal.susz@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