chore/115-manual-review-and-cleanup #128

Merged
hoogv merged 7 commits from chore/115-manual-review-and-cleanup into dev 2026-07-25 19:39:45 +00:00
Owner

Description

In this pull-request the code for the DSS hal has been revised a bit by removing the comments. This PR serves as another means to review the code once again.

Why

This PR and contribution improves the quality of the code and introduces another check/moment where the hal is once again reviewed by human eyes.

Closes #115

Type of Change

  • Chore / maintenance

Impact Assessment

  • Functional impact: None
  • Regulatory impact: None (only comments changed)
  • QMS impact: None
  • Risk impact: None

Testing

  • CI pipeline passes (compile, unit tests, integration tests, static analysis)
  • Manually tested:
  • No regressions observed in related areas

PR Size

  • XL (> 300 lines) — must split unless exemption declared

Size justification / exemption (if L or XL):

The size of PR is big due to the amount of comment lines being removed from 10 files. No code was changed.

Exemption

This PR contains removal of comments.
Excluded lines: ALL.
Effective reviewed lines: ALL

Checklist

  • Commit messages follow type(scope): description convention with Relates to #<issue> footer
  • PR template filled in completely
  • No unverified external binaries introduced (see QMS-GITFLOW-001 Binary Security section)
  • All commits leave the codebase in a compilable, passing-tests state (Commit Integrity Rule)
  • Reviewer assigned
  • QMS maintainer approval obtained (required for QMS and device repository changes)

Summary

No code was altered in this pr. Only comments.

## Description <!-- What does this PR do? Summarize the change in 1-3 sentences. --> In this pull-request the code for the DSS hal has been revised a bit by removing the comments. This PR serves as another means to review the code once again. ## Why <!-- Change justification per ISO 9001 section 7.5.2. Explain the rationale — why is this change necessary? What problem does it solve or requirement does it fulfill? Do NOT just restate what the code does. --> This PR and contribution improves the quality of the code and introduces another check/moment where the hal is once again reviewed by human eyes. ## Related Issue <!-- Every PR must close or relate to a tracked issue per QMS-GITFLOW-001. --> Closes #115 ## Type of Change - [x] Chore / maintenance ## Impact Assessment - **Functional impact:** None <!-- Does this change product behavior? Which features are affected? --> - **Regulatory impact:** None (only comments changed) <!-- Does this trigger compliance activities (CE, MDR, ISO)? --> - **QMS impact:** None <!-- Does any QMS procedure, record, or document need updating? --> - **Risk impact:** None <!-- Should the risk register be reviewed or updated? --> ## Testing <!-- Describe what was tested and how. CI must pass before merge. --> - [x] CI pipeline passes (compile, unit tests, integration tests, static analysis) - [x] Manually tested: <!-- describe scenario --> - [x] No regressions observed in related areas ## PR Size <!-- Per QMS-GITFLOW-001. Declare exemptions below if applicable. --> - [x] XL (> 300 lines) — must split unless exemption declared **Size justification / exemption (if L or XL):** The size of PR is big due to the amount of comment lines being removed from 10 files. No code was changed. ## Exemption This PR contains removal of comments. Excluded lines: ALL. Effective reviewed lines: ALL ## Checklist - [x] Commit messages follow `type(scope): description` convention with `Relates to #<issue>` footer - [x] PR template filled in completely - [x] No unverified external binaries introduced (see QMS-GITFLOW-001 Binary Security section) - [x] All commits leave the codebase in a compilable, passing-tests state (Commit Integrity Rule) - [x] Reviewer assigned - [x] QMS maintainer approval obtained (required for QMS and device repository changes) ## Summary <!-- Optional: bullet-point summary of the key changes for reviewers. Especially useful for larger PRs. --> No code was altered in this pr. Only comments.
This driver was written on-basis of the TI-hal with claude-code. Claude adds a
lot of comments to the code to keep track of its own changes. Fornutely most of it is churn and does not add to the quality of the driv
er and can be removed. Especially the comments about why loops are bounded, that's because I told him to in regards with MISRA and some
 registers being out-of-scope because not described in RM or the TI hal code.

Relates to #115

Signed-off-by: Victor Hogeweij <hogeweyv@gmail.com>
Trim and remove comments in the header so that the header and function description are less ambiguous to the developer.

Relates to #115

Signed-off-by: Victor Hogeweij <hogeweyv@gmail.com>
Remove redundant comments generated by claude in the modules.

Relates to #115

Signed-off-by: Victor Hogeweij <hogeweyv@gmail.com>
Remove redundant comments that would otherwise get out of date or hinders readability.

Relates to #115

Signed-off-by: Victor Hogeweij <hogeweyv@gmail.com>
Cleanup comments created by claude. As the output is very verbose and does not contribute to being in the code.

Relates to #115

Signed-off-by: Victor Hogeweij <hogeweyv@gmail.com>
Cleanup comments made by claude code. Which overly document the module.

Relates to #115

Signed-off-by: Victor Hogeweij <hogeweyv@gmail.com>
chore(hal_dss_rti): cleanup the comments in the hal_dss_rti module
All checks were successful
lint / clang-format (pull_request) Successful in 11s
tests / host-tests (pull_request) Successful in 46s
lint / misra (pull_request) Successful in 1m13s
lint / clang-format (push) Successful in 11s
tests / host-tests (push) Successful in 46s
lint / misra (push) Successful in 1m14s
e10e45bc99
The comments in the hal_dss_rti module were generated by claude and are overly verbose on certain parts and also irrelevant.

Relates to #115

Signed-off-by: Victor Hogeweij <hogeweyv@gmail.com>
hoogv added this to the Development project 2026-07-25 19:20:15 +00:00
hoogv self-assigned this 2026-07-25 19:20:16 +00:00
Sign in to join this conversation.
No reviewers
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
opendutchsolutions.public/hal_awr6843!128
No description provided.