From 0c65e1d7555d08b7b2faaf3a083d98e83f650bbe Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?J=2E=20Neusch=C3=A4fer?= Date: Thu, 15 Feb 2024 15:45:35 +0100 Subject: [PATCH] pico/mutex.h: Fix typo in comment (#1637) --- src/common/pico_sync/include/pico/mutex.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/common/pico_sync/include/pico/mutex.h b/src/common/pico_sync/include/pico/mutex.h index bcb3e99e3..75fa1ef5a 100644 --- a/src/common/pico_sync/include/pico/mutex.h +++ b/src/common/pico_sync/include/pico/mutex.h @@ -20,7 +20,7 @@ extern "C" { * * Mutexes are application level locks usually used protecting data structures that might be used by * multiple threads of execution. Unlike critical sections, the mutex protected code is not necessarily - * required/expected to complete quickly, as no other sytem wide locks are held on account of an acquired mutex. + * required/expected to complete quickly, as no other system wide locks are held on account of an acquired mutex. * * When acquired, the mutex has an owner (see \ref lock_get_caller_owner_id) which with the plain SDK is just * the acquiring core, but in an RTOS it could be a task, or an IRQ handler context.