commit 4772cf24aa659eb87efe24dcb62ef07dda360d80
author Masahiro Yamada <yamada.m@jp.panasonic.com> Tue Sep 16 16:33:00 2014 +0900
committer Tom Rini <trini@ti.com> Wed Sep 24 18:30:28 2014 -0400
tree c4c832cf17fc05ab564fb54a67f390d043b1e91d
parent 3f053fe262949cca4cfcb5a0e55d54bc3e384546

kconfig: move CONFIG_CMD_BOOTM to Kconfig

CONFIG_CMD_BOOTM is defined in config_cmd_defaults.h
which is forcebly included from each board.
So, the default value of "config CMD_BOOTM" should be "y".

For some boards undefining it (bf506f-ezkit, controlcenterd_TRAILBLA,
controlcenterd_TRAILBLAZER_DEVELOP, controlcenterd_TRAILBLAZER),
"# CONFIG_CMD_BOOTM is not set" should be added to their defconfig.

Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com>
Acked-by: Simon Glass <sjg@chromium.org>

configs/bf506f-ezkit_defconfig

diff --git a/configs/bf506f-ezkit_defconfig b/configs/bf506f-ezkit_defconfig
index f81f412..da25718 100644
--- a/configs/bf506f-ezkit_defconfig
+++ b/configs/bf506f-ezkit_defconfig
@@ -1,2 +1,3 @@
 CONFIG_BLACKFIN=y
 CONFIG_TARGET_BF506F_EZKIT=y
+# CONFIG_CMD_BOOTM is not set