Skip to content

Conversation

@github-actions
Copy link

Backport 98dfa0a from #93114.

K_TICKS_FOREVER is defined as -1. Guard logic has been added for the case
when `ticks - exit_latency_ticks == -1` to prevent sys_clock_set_timeout()
from incorrectly setting a forever timeout.

Signed-off-by: Serhiy Katsyuba <[email protected]>
(cherry picked from commit 98dfa0a)
@github-actions github-actions bot added the Backport Backport PR and backport failure issues label Jul 19, 2025
@github-project-automation github-project-automation bot moved this to To do in Backports Jul 19, 2025
@sonarqubecloud
Copy link

@danieldegrasse
Copy link
Contributor

This PR needs an issue attached in order to be eligible for backporting, @serhiy-katsyuba-intel can you please add one if you'd like to backport it?

@henrikbrixandersen henrikbrixandersen moved this from Needs more info to Needs a bug report in Backports Aug 4, 2025
@dkalowsk
Copy link
Contributor

@serhiy-katsyuba-intel still needs an issue. Do you have one?

@github-actions
Copy link
Author

This pull request has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this pull request will automatically be closed in 14 days. Note, that you can always re-open a closed pull request at any time.

@github-actions github-actions bot added the Stale label Oct 21, 2025
@github-actions github-actions bot removed the Stale label Oct 22, 2025
@dkalowsk dkalowsk removed this from the v4.2.1 milestone Oct 23, 2025
@dkalowsk dkalowsk added this to the 4.2.2 milestone Oct 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: Power Management Backport Backport PR and backport failure issues

Projects

Status: Needs a bug report

Development

Successfully merging this pull request may close these issues.

8 participants