Docs: comment typo fix (accomodates -> accommodates)
[lttng-tools.git] / include / lttng / notification / channel-internal.h
index efe502fe4f284a4830426ebe5250e71c217882ea..7343b03bba840fa3a66d984d1e6c24b99f4029c3 100644 (file)
 #include <pthread.h>
 #include <urcu/list.h>
 
+/*
+ * Protocol version change log:
+ * - v1.0
+ *   - Initial implementation of the notification channel protocol,
+ *   - Supported conditions are LOW/HIGH buffer usage conditions,
+ * - v1.1
+ *   - New condition type "LTTNG_CONDITION_TYPE_SESSION_CONSUMED_SIZE" added,
+ *   - New condition type "LTTNG_CONDITION_TYPE_SESSION_ROTATION_ONGOING" added,
+ *   - New condition type "LTTNG_CONDITION_TYPE_SESSION_ROTATION_COMPLETED" added,
+ */
 #define LTTNG_NOTIFICATION_CHANNEL_VERSION_MAJOR 1
-#define LTTNG_NOTIFICATION_CHANNEL_VERSION_MINOR 0
+#define LTTNG_NOTIFICATION_CHANNEL_VERSION_MINOR 1
 
 enum lttng_notification_channel_message_type {
        LTTNG_NOTIFICATION_CHANNEL_MESSAGE_TYPE_UNKNOWN = -1,
@@ -64,13 +74,13 @@ struct pending_notification {
 };
 
 /*
- * The notification channel protocol is bidirectional and accomodates
+ * The notification channel protocol is bidirectional and accommodates
  * synchronous and asynchronous communication modes:
  *
  *   - Synchronous: commands emitted by the client to which a reply is expected
  *     (e.g. subscribing/unsubscribing to conditions),
  *   - Asynchronous: notifications which are sent by the lttng_endpoint to the
- *     client as one of the subscribed condition has occured.
+ *     client as one of the subscribed condition has occurred.
  *
  * The nature of this hybrid communication mode means that asynchronous messages
  * (e.g. notifications) may be interleaved between synchronous messages (e.g. a
This page took 0.024866 seconds and 5 git commands to generate.