Jukka Rissanen cc528d37c2 net: syslog: Make sure CONFIG_LOG_IMMEDIATE is not set ... The immediate logging option cannot be used with network logging support CONFIG_LOG_BACKEND_NET as that would cause the generated rsyslog messages to be malformed. The UDP packets would only have one byte payloads which is not correct. So make sure that user is not able to select a configuration with immediate mode and network logging. Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>		2020-12-04 15:46:42 +02:00
..
mipi_syst	logging: add STP transport and raw data output support for syst	2020-11-17 10:09:19 -06:00
CMakeLists.txt	soc/intel_adsp: Unify trace backends	2020-11-17 12:28:10 -08:00
Kconfig	net: syslog: Make sure CONFIG_LOG_IMMEDIATE is not set	2020-12-04 15:46:42 +02:00
Kconfig.template.log_config
log_backend_adsp.c	soc/intel_adsp: Unify trace backends	2020-11-17 12:28:10 -08:00
log_backend_native_posix.c
log_backend_net.c
log_backend_rtt.c
log_backend_spinel.c
log_backend_swo.c
log_backend_uart.c
log_backend_xtensa_sim.c
log_cmds.c
log_core.c
log_list.c
log_list.h
log_minimal.c
log_msg.c
log_output_syst.c	logging: add STP transport and raw data output support for syst	2020-11-17 10:09:19 -06:00
log_output.c