aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDaniel Bevenius <[email protected]>2021-10-11 13:34:50 +0200
committerUlf Lilleengen <[email protected]>2021-10-11 13:55:05 +0200
commita7c37d2ff49de0cb002b27c2cf536d8371748485 (patch)
tree296aaf4c8bdc39c912eac39cc5aa1c322be6c56b
parent5ae276fe50d1445c9f2e8df3871b247f7d59fc0c (diff)
Fix typo in RunQueue documentation
-rw-r--r--embassy/src/executor/raw/run_queue.rs2
1 files changed, 1 insertions, 1 deletions
diff --git a/embassy/src/executor/raw/run_queue.rs b/embassy/src/executor/raw/run_queue.rs
index d0258c717..24624e1bd 100644
--- a/embassy/src/executor/raw/run_queue.rs
+++ b/embassy/src/executor/raw/run_queue.rs
@@ -24,7 +24,7 @@ impl RunQueueItem {
24/// null. Then the batch is iterated following the next pointers until null is reached. 24/// null. Then the batch is iterated following the next pointers until null is reached.
25/// 25///
26/// Note that batches will be iterated in the reverse order as they were enqueued. This is OK 26/// Note that batches will be iterated in the reverse order as they were enqueued. This is OK
27/// for our purposes: it can't crate fairness problems since the next batch won't run until the 27/// for our purposes: it can't create fairness problems since the next batch won't run until the
28/// current batch is completely processed, so even if a task enqueues itself instantly (for example 28/// current batch is completely processed, so even if a task enqueues itself instantly (for example
29/// by waking its own waker) can't prevent other tasks from running. 29/// by waking its own waker) can't prevent other tasks from running.
30pub(crate) struct RunQueue { 30pub(crate) struct RunQueue {