daemon: Remove the concept of triggering or suppressing events
Rather, trigger them (or not) as necessary in the relevant code-paths.
This ensures that any call to one of protocol_events_{set,clear}()
actually has a consequence that we can set about dealing with in the
transport layer.
Change-Id: If64733fa53ed9def0da8330c99cbe48327bab934
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
diff --git a/test/bmc_event_ack_v2.c b/test/bmc_event_ack_v2.c
index 51f026e..719c27b 100644
--- a/test/bmc_event_ack_v2.c
+++ b/test/bmc_event_ack_v2.c
@@ -50,7 +50,7 @@
rc = mbox_command_dispatch(ctx, get_info, sizeof(get_info));
assert(rc == 1);
- protocol_events_set(ctx, FLAGS, EVENT_TRIGGER);
+ protocol_events_set(ctx, FLAGS);
rc = mbox_command_dispatch(ctx, command, sizeof(command));
assert(rc == 1);