From cceec5ae325613306e81c7596472cf155e2a18d7 Mon Sep 17 00:00:00 2001 From: Josh Soref <2119212+jsoref@users.noreply.github.com> Date: Tue, 28 Jan 2025 21:17:02 -0500 Subject: [PATCH] spelling: tries Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> --- src/fw/services/normal/data_logging/dls_main.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/fw/services/normal/data_logging/dls_main.c b/src/fw/services/normal/data_logging/dls_main.c index 287ba3a4..d3a2dc5e 100644 --- a/src/fw/services/normal/data_logging/dls_main.c +++ b/src/fw/services/normal/data_logging/dls_main.c @@ -444,7 +444,7 @@ DataLoggingResult dls_log(DataLoggingSession *session, const void* data, uint32_ // // Some datalogging code holds the dls_list.c:s_list_mutex while taking the // bt_lock. Since we are locking the list and then trying to get the bt_lock, - // any other thread which holds the bt_lock and then trys to call a log could + // any other thread which holds the bt_lock and then tries to call a log could // result in a deadlock (since dls_lock_session() uses the list mutex). For non-release // builds assert when this happens so we can catch the cases and fix them. bt_lock_assert_held(false);