diff options
| author | bors[bot] <26634292+bors[bot]@users.noreply.github.com> | 2020-01-28 21:50:55 +0000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-01-28 21:50:55 +0000 |
| commit | d77270adc21bed8efe0302953cefc027e7a73042 (patch) | |
| tree | 13d1efafe30774946dd86779e05dd0b0163a37e7 /book/en/src/by-example/app.md | |
| parent | 60c14ef680c68593b2cadb24aa086d62973dcad5 (diff) | |
| parent | 1a1a1e21674d136a335d3955e0caf250d6af31eb (diff) | |
Merge #297
297: Reference the correct example in the by-example book r=japaric a=AfoHT
closes #298
Co-authored-by: Henrik Tjäder <henrik@tjaders.com>
Diffstat (limited to 'book/en/src/by-example/app.md')
| -rw-r--r-- | book/en/src/by-example/app.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/book/en/src/by-example/app.md b/book/en/src/by-example/app.md index f687194..5cace37 100644 --- a/book/en/src/by-example/app.md +++ b/book/en/src/by-example/app.md @@ -103,7 +103,7 @@ mut` variables are safe to use within a hardware task. ``` ``` console -$ cargo run --example interrupt +$ cargo run --example hardware {{#include ../../../../ci/expected/hardware.run}}``` So far all the RTFM applications we have seen look no different that the @@ -135,7 +135,7 @@ The following example showcases the priority based scheduling of tasks. ``` ``` console -$ cargo run --example interrupt +$ cargo run --example preempt {{#include ../../../../ci/expected/preempt.run}}``` Note that the task `gpiob` does *not* preempt task `gpioc` because its priority |