sys/xtimer: introduce xtimer_is_set()
#17630
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kaspar030
added
the
CI: ready for build
kaspar030
requested review from
aabadie,
fjmolinas,
leandrolanzieri,
MichelRottleuthner and
smlng
as code owners
github-actions
bot
added
Area: sys
benpicco
approved these changes
Feb 9, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Contribution description
There are cases where code is using internal xtimer struct members to figure out if a given xtimer is currentlly set. So, provide a function in the public API.
I've added some uses of this function (both ways, on set timers and unset timers) to
xtimer_remove().I consider this addition as an intermediate step, easing migration to ztimer_xtimer_compat.
Testing procedure
CI should be fine.
Issues/PRs references