From: Heinrich Schuchardt <xypron.glpk@gmx.de>
Date: Thu, 19 Apr 2018 20:02:46 +0000 (+0200)
Subject: cmd: CONFIG_CMD_LOG select CONFIG_LOG
X-Git-Tag: v2018.05-rc3~25
X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=83a1f933d141ca5db69344559c1eef255d45fddd;hp=9adc78d278bec84b638aa3b25b102f3cfb21438c;p=u-boot

cmd: CONFIG_CMD_LOG select CONFIG_LOG

CONFIG_CMD_LOG without CONFIG_LOG leads to a build error:
‘gd_t {aka volatile struct global_data}’ has no member named
‘default_log_level’

So CMD_LOG should select LOG.

Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
Reviewed-by: Simon Glass <sjg@chromium.org>
---

diff --git a/cmd/Kconfig b/cmd/Kconfig
index bc1d2f31c0..225bb002a6 100644
--- a/cmd/Kconfig
+++ b/cmd/Kconfig
@@ -1660,6 +1660,7 @@ config CMD_KGDB
 
 config CMD_LOG
 	bool "log - Generation, control and access to logging"
+	select LOG
 	help
 	  This provides access to logging features. It allows the output of
 	  log data to be controlled to a limited extent (setting up the default