Tracking issue for deferred backporting fixes
Open
@pamaury is already working on this.
Since Aug 8, 2025.
- Dominant language
- SystemVerilog
- Stars
- 3.6k
- Forks
- 1.1k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 141
Description
### Description
In the course of the backporting effort from earlgrey_1.0.0 to master, several issues have been found. To avoid difficult conflicts, we have sometimes decided to merge changes as-is even if it is not ideal. This issues tracks such instances so that we can fix the code when the backporting is done
- https://github.com/lowRISC/opentitan/pull/27834#pullrequestreview-3098365940
- https://github.com/lowRISC/opentitan/pull/27747#discussion_r2260825429
- https://github.com/lowRISC/opentitan/pull/27878#discussion_r2273391876 (when we switch to bazel 8.1)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.