[rom_ext] Evaluate consolidating boot_svc response structs
Open
Nobody has claimed this yet.
SW:ROM_EXT
- Dominant language
- SystemVerilog
- Stars
- 3.6k
- Forks
- 1.1k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 141
Description
Description
Several boot_svc response structs have the exact same structure:
struct foo_response {
rom_error_t status;
};
Consider consolidating into a single definition.
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.
Research direction
Start by locating the boot_svc response struct definitions in the rom_ext sources and comparing their fields, especially the shared rom_error_t status member. Determine which definitions can be consolidated without changing the boot service interface, then run the relevant rom_ext build or tests to confirm the response types remain compatible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- embedded-iot, security
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100