sys/include/xtimer.h: deprecate nanosleep#17296
Merged
aabadie merged 3 commits intoRIOT-OS:masterfrom Dec 1, 2021
Merged
Conversation
fjmolinas
added
the
Process: deprecation
fjmolinas
requested review from
basilfx,
cgundogan,
jia200x and
leandrolanzieri
as code owners
github-actions
bot
added
Area: drivers
basilfx
reviewed
Nov 30, 2021
maribu
approved these changes
Nov 30, 2021
Member
maribu
left a comment
maribu
left a comment
There was a problem hiding this comment.
ACK. Please squash in the typo fixes right away.
fjmolinas
force-pushed
the
pr_nanosleep_deprecate
branch
from
42fe808 to
197fb4a
Compare
benpicco
reviewed
Nov 30, 2021
fjmolinas
force-pushed
the
pr_nanosleep_deprecate
branch
from
197fb4a to
92a003f
Compare
benpicco
added
CI: ready for build
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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
This PR deprecates
nanosleep, realistically this made no sense since no backend was able at running at this speed.Testing procedure
A green ci should be enough...