ea71a49292
Resolves: #2161260,#2170883,#2178222,#2190226,#2209912,#2211065,#2213521,#2226980,#2230364,#2231845
26 lines
1.1 KiB
Diff
26 lines
1.1 KiB
Diff
From 9974ff3bce3b309f086585929b21ac29d4d4f582 Mon Sep 17 00:00:00 2001
|
|
From: Daan De Meyer <daan.j.demeyer@gmail.com>
|
|
Date: Wed, 24 May 2023 11:41:37 +0200
|
|
Subject: [PATCH] timer: Use dual_timestamp_is_set() in one more place
|
|
|
|
(cherry picked from commit e21f75afcd95a46261a36a2614712eff6bc119f4)
|
|
|
|
Related: #2211065
|
|
---
|
|
src/core/timer.c | 2 +-
|
|
1 file changed, 1 insertion(+), 1 deletion(-)
|
|
|
|
diff --git a/src/core/timer.c b/src/core/timer.c
|
|
index 711500313d..60e8fea79f 100644
|
|
--- a/src/core/timer.c
|
|
+++ b/src/core/timer.c
|
|
@@ -399,7 +399,7 @@ static void timer_enter_waiting(Timer *t, bool time_change) {
|
|
* to that. If we don't, just start from
|
|
* the activation time. */
|
|
|
|
- if (t->last_trigger.realtime > 0)
|
|
+ if (dual_timestamp_is_set(&t->last_trigger))
|
|
b = t->last_trigger.realtime;
|
|
else if (dual_timestamp_is_set(&UNIT(t)->inactive_exit_timestamp))
|
|
b = UNIT(t)->inactive_exit_timestamp.realtime;
|