aboutsummaryrefslogtreecommitdiffhomepage
path: root/src/core/iomgr/alarm.h
diff options
context:
space:
mode:
Diffstat (limited to 'src/core/iomgr/alarm.h')
-rw-r--r--src/core/iomgr/alarm.h4
1 files changed, 2 insertions, 2 deletions
diff --git a/src/core/iomgr/alarm.h b/src/core/iomgr/alarm.h
index 30cffa94a5..dc4ce29b46 100644
--- a/src/core/iomgr/alarm.h
+++ b/src/core/iomgr/alarm.h
@@ -55,7 +55,7 @@ typedef struct grpc_alarm
and application code should check the status to determine how it was
invoked. The application callback is also responsible for maintaining
information about when to free up any user-level state. */
-void grpc_alarm_init (grpc_alarm * alarm, gpr_timespec deadline, grpc_iomgr_cb_func alarm_cb, void *alarm_cb_arg, gpr_timespec now, grpc_closure_list * closure_list);
+void grpc_alarm_init (grpc_exec_ctx * exec_ctx, grpc_alarm * alarm, gpr_timespec deadline, grpc_iomgr_cb_func alarm_cb, void *alarm_cb_arg, gpr_timespec now);
/* Note that there is no alarm destroy function. This is because the
alarm is a one-time occurrence with a guarantee that the callback will
@@ -83,6 +83,6 @@ void grpc_alarm_init (grpc_alarm * alarm, gpr_timespec deadline, grpc_iomgr_cb_f
matches this aim.
Requires: cancel() must happen after add() on a given alarm */
-void grpc_alarm_cancel (grpc_alarm * alarm, grpc_closure_list * closure_list);
+void grpc_alarm_cancel (grpc_exec_ctx * exec_ctx, grpc_alarm * alarm);
#endif /* GRPC_INTERNAL_CORE_IOMGR_ALARM_H */