[Backport v4.2-branch] pm: Fix to prevent incorrect forever timeout#93367
[Backport v4.2-branch] pm: Fix to prevent incorrect forever timeout#93367github-actions[bot] wants to merge 1 commit intov4.2-branchfrom
Conversation
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 <serhiy.katsyuba@intel.com> (cherry picked from commit 98dfa0a)
zephyrbot
requested review from
JordanYates,
bjarki-andreasen,
ceolin,
nashif,
teburd and
tmleman
|
|
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? |
|
@serhiy-katsyuba-intel still needs an issue. Do you have one? |
|
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. |
|
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. |
7 participants
Backport 98dfa0a from #93114.