diff options
Diffstat (limited to 'book/en/src/by-example')
| -rw-r--r-- | book/en/src/by-example/app.md | 4 | ||||
| -rw-r--r-- | book/en/src/by-example/resources.md | 6 | ||||
| -rw-r--r-- | book/en/src/by-example/timer-queue.md | 2 | ||||
| -rw-r--r-- | book/en/src/by-example/tips.md | 2 |
4 files changed, 7 insertions, 7 deletions
diff --git a/book/en/src/by-example/app.md b/book/en/src/by-example/app.md index ebb71f1..f687194 100644 --- a/book/en/src/by-example/app.md +++ b/book/en/src/by-example/app.md @@ -13,9 +13,9 @@ point to a *peripheral access crate* (PAC) generated using [`svd2rust`] **v0.14.x** or newer. The `app` attribute will expand into a suitable entry point so it's not required to use the [`cortex_m_rt::entry`] attribute. -[`app`]: ../../api/cortex_m_rtfm_macros/attr.app.html +[`app`]: ../../../api/cortex_m_rtfm_macros/attr.app.html [`svd2rust`]: https://crates.io/crates/svd2rust -[`cortex_m_rt::entry`]: ../../api/cortex_m_rt_macros/attr.entry.html +[`cortex_m_rt::entry`]: ../../../api/cortex_m_rt_macros/attr.entry.html > **ASIDE**: Some of you may be wondering why we are using a `const` item as a > module and not a proper `mod` item. The reason is that using attributes on diff --git a/book/en/src/by-example/resources.md b/book/en/src/by-example/resources.md index e8f61d5..b33ca9b 100644 --- a/book/en/src/by-example/resources.md +++ b/book/en/src/by-example/resources.md @@ -46,8 +46,8 @@ instead of a reference. This resource proxy is a structure that implements the [`Mutex`] trait. The only method on this trait, [`lock`], runs its closure argument in a critical section. -[`Mutex`]: ../../api/rtfm/trait.Mutex.html -[`lock`]: ../../api/rtfm/trait.Mutex.html#method.lock +[`Mutex`]: ../../../api/rtfm/trait.Mutex.html +[`lock`]: ../../../api/rtfm/trait.Mutex.html#method.lock The critical section created by the `lock` API is based on dynamic priorities: it temporarily raises the dynamic priority of the context to a *ceiling* @@ -89,7 +89,7 @@ consumer and producer end points in `init` and then each end point is stored in a different resource; `UART0` owns the producer resource and `idle` owns the consumer resource. -[`Queue`]: ../../api/heapless/spsc/struct.Queue.html +[`Queue`]: ../../../api/heapless/spsc/struct.Queue.html ``` rust {{#include ../../../../examples/late.rs}} diff --git a/book/en/src/by-example/timer-queue.md b/book/en/src/by-example/timer-queue.md index 57e9d01..7c8be38 100644 --- a/book/en/src/by-example/timer-queue.md +++ b/book/en/src/by-example/timer-queue.md @@ -20,7 +20,7 @@ type (see [`core::time::Duration`]) and this `Duration` type must implement the integer. If the result of the conversion doesn't fit in a 32-bit number then the operation must return an error, any error type. -[`Monotonic`]: ../../api/rtfm/trait.Monotonic.html +[`Monotonic`]: ../../../api/rtfm/trait.Monotonic.html [std-instant]: https://doc.rust-lang.org/std/time/struct.Instant.html [`core::time::Duration`]: https://doc.rust-lang.org/core/time/struct.Duration.html diff --git a/book/en/src/by-example/tips.md b/book/en/src/by-example/tips.md index 3852b44..a008206 100644 --- a/book/en/src/by-example/tips.md +++ b/book/en/src/by-example/tips.md @@ -16,7 +16,7 @@ one can write a generic function that operates on generic resources and call it from different tasks to perform some operation on the same set of resources. Here's one such example: -[`rtfm::Exclusive`]: ../../api/rtfm/struct.Exclusive.html +[`rtfm::Exclusive`]: ../../../api/rtfm/struct.Exclusive.html ``` rust {{#include ../../../../examples/generics.rs}} |