X-Git-Url: https://git.lttng.org/?p=lttng-tools.git;a=blobdiff_plain;f=include%2Flttng%2Fnotification%2Fnotification-internal.h;h=65b03672295f638250e90ce93edb5c31ef8a0e83;hp=648977f3378ff804ba542ddccd83cb07a74134c2;hb=9b63a4aa352c184984395c097f86d5e54c295012;hpb=577983cb5ac581ff691d650bd6c5c68719feb31f

diff --git a/include/lttng/notification/notification-internal.h b/include/lttng/notification/notification-internal.h
index 648977f33..65b036722 100644
--- a/include/lttng/notification/notification-internal.h
+++ b/include/lttng/notification/notification-internal.h
@@ -29,21 +29,6 @@
 struct lttng_notification {
 	struct lttng_condition *condition;
 	struct lttng_evaluation *evaluation;
-	/*
-	 * The ownership of the notification's inner-elements depends
-	 * on the way it was created. The notification owns both
-	 * the condition and evaluation if it was obtained from a notification
-	 * channel (i.e. created using lttng_notification_create_from_buffer)
-	 * as the user may never access the condition and evaluation,
-	 * thus never getting a chance to free them.
-	 *
-	 * However, when the _private_ lttng_notification_create() function
-	 * is used, no ownership of condition and evaluation is assumed by
-	 * the notification object. The main reason for this change in
-	 * behavior is that internal users of this API only use the object
-	 * to use its serialization facilities.
-	 */
-	bool owns_elements;
 };
 
 struct lttng_notification_comm {
@@ -59,7 +44,7 @@ struct lttng_notification *lttng_notification_create(
 		struct lttng_evaluation *evaluation);
 
 LTTNG_HIDDEN
-int lttng_notification_serialize(struct lttng_notification *notification,
+int lttng_notification_serialize(const struct lttng_notification *notification,
 		struct lttng_dynamic_buffer *buf);
 
 LTTNG_HIDDEN