drivers: fix utubettl next_event after release - #261
Merged
Merged
Conversation
Col-Waltz
force-pushed
the
Col-Waltz/delayed-ttl-after-release
branch
from
September 15, 2026 12:27
ded4e51 to
04c1a39
Compare
oleg-jukovec
requested changes
Sep 15, 2026
Col-Waltz
force-pushed
the
Col-Waltz/delayed-ttl-after-release
branch
from
September 15, 2026 14:57
04c1a39 to
fb4b10a
Compare
oleg-jukovec
requested changes
Sep 15, 2026
Each task has `next_event` value in microseconds. At the release of the task without delay this value was again converted to microseconds which resulted in multiplication by 10^6. For task in `READY` status after release `next_event` means time to delete task.
Col-Waltz
force-pushed
the
Col-Waltz/delayed-ttl-after-release
branch
from
September 15, 2026 21:40
fb4b10a to
7218200
Compare
oleg-jukovec
approved these changes
Sep 16, 2026
palage4a
approved these changes
Sep 18, 2026
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
3 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.
Each task has
next_eventvalue in microseconds. At the release of the task without delay this value was again converted to microseconds which resulted in multiplication by 10^6. For task inREADYstatus after releasenext_eventmeans time to delete task.