Skip to contentSkip to conversation

cmd: CONFIG_CMD_LOG select CONFIG_LOG

PATCH New Heinrich Schuchardt 3 participants 3 messages Apr 19, 2018 – Apr 28, 2018

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 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.

---
 cmd/Kconfig | 1 +
 1 file changed, 1 insertion(+)
cmd/Kconfig +1 -0
index bc1d2f31c0..225bb002a6 100644
@@ -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
Signature · 1 line
2.15.1
#2 lore raw

PATCH 1/1 cmd: CONFIG_CMD_LOG select CONFIG_LOG

In reply to Heinrich Schuchardt
Quoted 8 lines · Heinrich Schuchardt

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.

Applied to u-boot/master, thanks!

Signature · 8 lines
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180428/0d6cf38b/attachment.sig>