Labels

• bad svd robustness

  this issue is caused by not handling svds that are not fully to specification
• breaking-change
• bug
• decision-accepted
• duplicate
• enhancement
• help wanted
• individual chip problem

  This issue describes an issue with a particular chip
• invalid
• missing svd feature

  This issue is caused by a lack of support for something in the svd specification
• needs-decision
• no changelog

  no-changelog
• nominated

  Issue nominated as discussion topic for the Embedded WG meeting
• pending close

  Issue will be closed if no further comments
• question
• S-blocked

  Status: marked as blocked ❌ on something else such as an RFC or other implementation work.
• S-blocked-closed
• S-inactive-closed

  Status: closed due to inactivity.
• S-waiting-on-author

  Status: The marked PR is awaiting some action (such as code changes) from the PR author.
• S-waiting-on-bikeshed

  Status: Awaiting a decision on trivial things.
• S-waiting-on-bors

  Status: Waiting on bors to run and complete tests.
• S-waiting-on-review

  Status: Awaiting review from the assignee but also interested parties.
• S-waiting-on-team

  Status: Awaiting decision from the relevant subteam (see the T-<team> label).
• T-tools
• wontfix