Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

core/debug: extend doc about DEBUG() / LOG_DEBUG() #21276

Merged
merged 1 commit into from
Mar 6, 2025

Conversation

maribu
Copy link
Member

@maribu maribu commented Mar 6, 2025

Contribution description

This adds a few lines to explain the difference between the two and hints when to use which.

Testing procedure

The CI will generate a preview of the doc that can be checked.

Issues/PRs references

None

@maribu maribu requested a review from kaspar030 as a code owner March 6, 2025 18:47
@maribu maribu added Area: doc Area: Documentation CI: ready for build If set, CI server will compile all applications for all available boards for the labeled PR labels Mar 6, 2025
@github-actions github-actions bot added Area: core Area: RIOT kernel. Handle PRs marked with this with care! and removed Area: doc Area: Documentation labels Mar 6, 2025
@riot-ci
Copy link

riot-ci commented Mar 6, 2025

Murdock results

✔️ PASSED

ef2d6f8 core/debug: extend doc about DEBUG() / LOG_DEBUG()

Success Failures Total Runtime
1 0 1 01m:22s

Artifacts

@maribu maribu added the Process: needs >1 ACK Integration Process: This PR requires more than one ACK label Mar 6, 2025
@github-actions github-actions bot added the Process: missing approvals Integration Process: PR needs more ACKS (handled by action) label Mar 6, 2025
@maribu
Copy link
Member Author

maribu commented Mar 6, 2025

While this PR isn't exactly scary, let's have a 2nd ACK as it is touching core.

@maribu maribu enabled auto-merge March 6, 2025 19:07
@crasbe
Copy link
Contributor

crasbe commented Mar 6, 2025

One might argue that it would be nicer to write DEBUG() instead of DEBUG as well, at least in the two notes, for consistency with the LOG_DEBUG(). But that's being pedandic I guess 😅

@crasbe
Copy link
Contributor

crasbe commented Mar 6, 2025

The generated documentation works now, but the new PR only changes the first LOG_DEBUG. There is another suggestion between the screenshots. Maybe I should've selected a bigger code block and just done one suggestion.

IMO you can squash directly and then it's good to merge from my side.

This adds a few lines to explain the difference between the two and
hints when to use which.

Co-authored-by: crasbe <[email protected]>
@maribu
Copy link
Member Author

maribu commented Mar 6, 2025

Done, should be good now :)

@github-actions github-actions bot removed the Process: missing approvals Integration Process: PR needs more ACKS (handled by action) label Mar 6, 2025
@maribu maribu added this pull request to the merge queue Mar 6, 2025
Merged via the queue into RIOT-OS:master with commit 20f0691 Mar 6, 2025
26 of 27 checks passed
@maribu maribu deleted the core/doc/debug branch March 6, 2025 21:15
@maribu
Copy link
Member Author

maribu commented Mar 6, 2025

Thx :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: core Area: RIOT kernel. Handle PRs marked with this with care! CI: ready for build If set, CI server will compile all applications for all available boards for the labeled PR Process: needs >1 ACK Integration Process: This PR requires more than one ACK
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants