aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDario Nieuwenhuis <[email protected]>2023-08-15 17:24:28 +0000
committerGitHub <[email protected]>2023-08-15 17:24:28 +0000
commit96e0ace89e48cffd073749cc3b08835a0a7d6cc9 (patch)
tree0df5db4a0ee7c8f5a6715ff554324a695c4621f1
parent7d24e433d835ba35aa7189f931c5731981c89bcf (diff)
parent8655ba110c95777c3edab3aabef34ae71d64957a (diff)
Merge pull request #1781 from bugadani/typo
Fix typo
-rw-r--r--embassy-sync/src/blocking_mutex/raw.rs2
1 files changed, 1 insertions, 1 deletions
diff --git a/embassy-sync/src/blocking_mutex/raw.rs b/embassy-sync/src/blocking_mutex/raw.rs
index 15796f1b2..a8afcad34 100644
--- a/embassy-sync/src/blocking_mutex/raw.rs
+++ b/embassy-sync/src/blocking_mutex/raw.rs
@@ -11,7 +11,7 @@ use core::marker::PhantomData;
11/// 11///
12/// Note that, unlike other mutexes, implementations only guarantee no 12/// Note that, unlike other mutexes, implementations only guarantee no
13/// concurrent access from other threads: concurrent access from the current 13/// concurrent access from other threads: concurrent access from the current
14/// thread is allwed. For example, it's possible to lock the same mutex multiple times reentrantly. 14/// thread is allowed. For example, it's possible to lock the same mutex multiple times reentrantly.
15/// 15///
16/// Therefore, locking a `RawMutex` is only enough to guarantee safe shared (`&`) access 16/// Therefore, locking a `RawMutex` is only enough to guarantee safe shared (`&`) access
17/// to the data, it is not enough to guarantee exclusive (`&mut`) access. 17/// to the data, it is not enough to guarantee exclusive (`&mut`) access.