From cccee18918a9bcc1b34ddcd33f219a4ed26fc690 Mon Sep 17 00:00:00 2001
From: Masahiro Yamada <yamada.m@jp.panasonic.com>
Date: Tue, 16 Sep 2014 16:33:02 +0900
Subject: kconfig: move CONFIG_CMD_EXPORTENV to Kconfig

Since CONFIG_CMD_EXPORTENV is defined in config_cmd_defaults.h,
it should be enabled for all the boards except bf506f-ezkit
that undefs it explicitely.

Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com>
Acked-by: Simon Glass <sjg@chromium.org>
Tested-by: Simon Glass <sjg@chromium.org>
---
 configs/bf506f-ezkit_defconfig | 1 +
 1 file changed, 1 insertion(+)

(limited to 'configs')

diff --git a/configs/bf506f-ezkit_defconfig b/configs/bf506f-ezkit_defconfig
index da25718709..09c9899ca3 100644
--- a/configs/bf506f-ezkit_defconfig
+++ b/configs/bf506f-ezkit_defconfig
@@ -1,3 +1,4 @@
 CONFIG_BLACKFIN=y
 CONFIG_TARGET_BF506F_EZKIT=y
 # CONFIG_CMD_BOOTM is not set
+# CONFIG_CMD_EXPORTENV is not set
-- 
cgit v1.2.1