From 8c7c902a83052a09159dcdbc50ffffd2d66aafa3 Mon Sep 17 00:00:00 2001 From: Mateusz Majewski Date: Wed, 19 Jan 2022 13:20:19 +0100 Subject: [PATCH] Fix some invalid function names in dlogutil.h documentation Change-Id: I50a44e3b27fd913c3d4a15ac9ee14f5e2fbcdb2d --- include/dlogutil.h | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/include/dlogutil.h b/include/dlogutil.h index 34107a8..f5d472f 100644 --- a/include/dlogutil.h +++ b/include/dlogutil.h @@ -118,7 +118,7 @@ int dlogutil_entry_get_message(const dlogutil_entry_s *entry, const char **msg); /** * @brief Retrieves the timestamp of the log entry. * @since_tizen 6.0 - * @remarks The information about timestamp availability can be retrieved using the dlogutil_get_traits() function. + * @remarks The information about timestamp availability can be retrieved using the dlogutil_buffer_check_ts_type_available() function. * For information on the timespec struct, refer to the clock_gettime(2) manpage. * @param[in] entry Log entry * @param[in] order Which timestamp to extract. #DLOGUTIL_SORT_DEFAULT is NOT allowed currently @@ -128,7 +128,7 @@ int dlogutil_entry_get_message(const dlogutil_entry_s *entry, const char **msg); * @retval TIZEN_ERROR_INVALID_PARAMETER Invalid value of order * @retval TIZEN_ERROR_INVALID_PARAMETER One of the pointers was NULL * @retval TIZEN_ERROR_NO_DATA The timestamp is missing - * @see dlogutil_get_traits() + * @see dlogutil_buffer_check_ts_type_available() */ int dlogutil_entry_get_timestamp(const dlogutil_entry_s *entry, dlogutil_sorting_order_e order, struct timespec *ts); @@ -277,7 +277,7 @@ int dlogutil_config_buffer_add(dlogutil_config_s *config, log_id_t buf); /** * @brief Enables full dump mode. * @since_tizen 6.0 - * @see dlogutil_get_logs_dump() + * @see dlogutil_config_mode_set_dump() */ #define DLOGUTIL_MAX_DUMP_SIZE UINT_MAX @@ -480,7 +480,7 @@ int dlogutil_buffer_get_default_ts_type(log_id_t buffer, dlogutil_sorting_order_ * @since_tizen 6.0 * @remarks If false is returned, the timestamp may still be available in some of the logs. * However, if true is returned, the timestamp will always be available. - * You can check the timestamp availability per log using the dlogutil_entry_get_ts() function. + * You can check the timestamp availability per log using the dlogutil_entry_get_timestamp() function. * @bug This is currently evaluated using the config file, which can change at runtime. In particular, * this can desync from the value of the server if the config file changes. Note that this is mostly * a theoretical concern, since the file is not intended to change during the runtime (the daemon asks -- 2.7.4