Vadim Yanitskiy 4b46b7eb53 vty/logging: logp: properly handle library specific sub-systems ... The library specific sub-systems are kind of special, because their position in the 'osmo_log_info' may vary depending on the number of application specific sub-systems. This is why their associated constant values (like DLGLOBAL) are negative, and this is what the LOGP() macro expects as the first argument. Before this change, invoking 'logp' command with any library specific logging sub-system would result in getting messages printed with the fall-back DLGLOBAL sub-systems. Change-Id: If86563e169fe1243adfa7b09c9d65d9f88c8a99e		2021-04-12 12:15:17 +00:00
..
logging_test.c	Drop use of log_set_print_filename() API inside libosmocore	2021-02-20 17:13:58 +00:00
logging_test.err	fix logging: log_set_category_filter() for internal DL* logging cats	2016-12-12 16:56:54 +01:00
logging_test.ok	logging: Move the logging test from OpenBSC into libosmocore	2012-09-27 16:29:54 +02:00
logging_vty_test.c	logging: Introduce mutex API to manage log_target in multi-thread envs	2019-10-09 14:19:52 +02:00
logging_vty_test.vty	vty/logging: logp: properly handle library specific sub-systems	2021-04-12 12:15:17 +00:00