diff --git a/.github/workflows/matrix-bot.yml b/.github/workflows/matrix-bot.yml index 6ef6787e5d..bc985d92d8 100644 --- a/.github/workflows/matrix-bot.yml +++ b/.github/workflows/matrix-bot.yml @@ -5,7 +5,7 @@ on: jobs: new-pr: - if: github.event.action == 'opened' && github.repository == 'rtic-rs/cortex-m-rtic' + if: github.event.action == 'opened' && github.repository == 'rtic-rs/rtic' runs-on: ubuntu-latest continue-on-error: true steps: @@ -18,7 +18,7 @@ jobs: server: "matrix.org" merged-pr: - if: github.event.action == 'closed' && github.event.pull_request.merged == true && github.repository == 'rtic-rs/cortex-m-rtic' + if: github.event.action == 'closed' && github.event.pull_request.merged == true && github.repository == 'rtic-rs/rtic' runs-on: ubuntu-latest continue-on-error: true steps: @@ -31,7 +31,7 @@ jobs: server: "matrix.org" abandoned-pr: - if: github.event.action == 'closed' && github.event.pull_request.merged == false && github.repository == 'rtic-rs/cortex-m-rtic' + if: github.event.action == 'closed' && github.event.pull_request.merged == false && github.repository == 'rtic-rs/rtic' runs-on: ubuntu-latest continue-on-error: true steps: diff --git a/book/en/book.toml b/book/en/book.toml index 25f841aefc..8a89eebd6c 100644 --- a/book/en/book.toml +++ b/book/en/book.toml @@ -17,6 +17,6 @@ create-missing = false command = "mdbook-mermaid" [output.html] -git-repository-url = "https://github.com/rtic-rs/cortex-m-rtic" +git-repository-url = "https://github.com/rtic-rs/rtic" git-repository-icon = "fa-github" additional-js = ["mermaid.min.js", "mermaid-init.js"] diff --git a/book/en/src/by-example/hardware_tasks.md b/book/en/src/by-example/hardware_tasks.md index c9022674bd..75dd1a4cc0 100644 --- a/book/en/src/by-example/hardware_tasks.md +++ b/book/en/src/by-example/hardware_tasks.md @@ -10,7 +10,7 @@ All tasks bound to an explicit interrupt are called *hardware tasks* since they Specifying a non-existing interrupt name will cause a compilation error. The interrupt names are commonly defined by [PAC or HAL][pacorhal] crates. -Any available interrupt vector should work. Specific devices may bind specific interrupt priorities to specific interrupt vectors outside user code control. See for example the [nRF “softdevice”](https://github.com/rtic-rs/cortex-m-rtic/issues/434). +Any available interrupt vector should work. Specific devices may bind specific interrupt priorities to specific interrupt vectors outside user code control. See for example the [nRF “softdevice”](https://github.com/rtic-rs/rtic/issues/434). Beware of using interrupt vectors that are used internally by hardware features; RTIC is unaware of such hardware specific details. diff --git a/book/en/src/internals/targets.md b/book/en/src/internals/targets.md index efad15005f..3562eefd22 100644 --- a/book/en/src/internals/targets.md +++ b/book/en/src/internals/targets.md @@ -7,7 +7,7 @@ ARMv8-M-base architectures, which forces RTIC to use source masking instead. For of lock and a detailed commentary of pros and cons, see the implementation of [lock in src/export.rs][src_export]. -[src_export]: https://github.com/rtic-rs/cortex-m-rtic/blob/master/src/export.rs +[src_export]: https://github.com/rtic-rs/rtic/blob/master/src/export.rs These differences influence how critical sections are realized, but functionality should be the same except that ARMv6-M/ARMv8-M-base cannot have tasks with shared resources bound to exception