df8d4e96ef
The documentation says a module can be split up over multiple files, but there's no good way to do that. In the file with the LOG_MODULE_REGISTER() call, the definitions of the module's state variables serve as declarations that LOG_DBG(), etc. can use. But in other files making up the module, no such declarations are available, and the macro expansion bombs out spectacularly and confusingly. Fix this by adding a LOG_MODULE_DECLARE() macro which other files in the module can use to declare the internal state used by the log module, so that LOG_DBG() etc. work properly. Keep the documentation up to date. Signed-off-by: Marti Bolivar <marti@foundries.io> |
||
|---|---|---|
| .. | ||
| event_logger.h | ||
| kernel_event_logger.h | ||
| log.h | ||
| log_backend.h | ||
| log_backend_uart.h | ||
| log_core.h | ||
| log_ctrl.h | ||
| log_instance.h | ||
| log_msg.h | ||
| log_output.h | ||
| sys_log.h | ||