X-Git-Url: https://git.lttng.org/?p=lttng-tools.git;a=blobdiff_plain;f=include%2Flttng%2Ftrigger%2Ftrigger.h;h=3b1cedda1fb4709457537ded9df978e206d6d3ca;hp=de4e93d70705bbb9787eb4e2a2e3faa54d152f18;hb=2c30250238cbd1c1976aca903cacc4abbb4f59ce;hpb=6dcf80d3521804571f64844853d976d6fe16ebc7

diff --git a/include/lttng/trigger/trigger.h b/include/lttng/trigger/trigger.h
index de4e93d70..3b1cedda1 100644
--- a/include/lttng/trigger/trigger.h
+++ b/include/lttng/trigger/trigger.h
@@ -49,8 +49,11 @@ enum lttng_trigger_firing_policy {
  * in the emission of a notification to clients listening through
  * notification channels.
  *
- * The caller retains the ownership of both the condition and action
- * and both must be kept alive for the lifetime of the trigger object.
+ * Prior to 2.13, the caller had to retain the ownership of both the condition
+ * and action. Both objects had to be kept alive for the lifetime of the trigger
+ * object. This is no longer the case as the condition and action objects are
+ * internally reference counted. It is safe to destroy a condition and an action
+ * after using them to create a trigger. However, they should no longer be used.
  *
  * If the action is a notification action with capture descriptors,
  * the condition must be an event rule condition.