[U-Boot] [PATCH v3 3/7] kconfig: Adjust ordering so that defaults work as expected

[Masahiro Yamada]

From: Simon Glass <sjg at chromium.org>

At present defaults in arch-specific Kconfig files are ignored if the
top-level item comes ahead of it in include order. This means that it is
not possible to have a U-Boot default that architectures and boards can
override. This does not seem very useful.

Move the include earlier to support this.

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

Changes in v3:
  - The same as what Simon posted
    http://patchwork.ozlabs.org/patch/441670/
    Included in this series to clarify the order

Changes in v2: None

 Kconfig | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/Kconfig b/Kconfig
index d40f9ec..351e5c9 100644
--- a/Kconfig
+++ b/Kconfig
@@ -12,6 +12,9 @@ config KCONFIG_OBJDIR
 	string
 	option env="KCONFIG_OBJDIR"
 
+# Allow defaults in arch-specific code to override any given here
+source "arch/Kconfig"
+
 menu "General setup"
 
 config LOCALVERSION
@@ -171,8 +174,6 @@ config SYS_CLK_FREQ
 
 endmenu		# Boot images
 
-source "arch/Kconfig"
-
 source "common/Kconfig"
 
 source "dts/Kconfig"
-- 
1.9.1