Move to kernel style SPDX license identifiers

[babeltrace.git] / include / babeltrace2 / trace-ir / stream.h

diff --git a/include/babeltrace2/trace-ir/stream.h b/include/babeltrace2/trace-ir/stream.h
index 32bc98e1770decbad7e3db38da584a301d896899..95f17a7f118a7d17dfa2973fd0a6fd624d17a1c4 100644 (file)
--- a/include/babeltrace2/trace-ir/stream.h
+++ b/include/babeltrace2/trace-ir/stream.h
@@ -1,28 +1,12 @@
-#ifndef BABELTRACE2_TRACE_IR_STREAM_H
-#define BABELTRACE2_TRACE_IR_STREAM_H
-
 /*
- * Copyright (c) 2010-2019 EfficiOS Inc. and Linux Foundation
- *
- * Permission is hereby granted, free of charge, to any person obtaining a copy
- * of this software and associated documentation files (the "Software"), to deal
- * in the Software without restriction, including without limitation the rights
- * to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
- * copies of the Software, and to permit persons to whom the Software is
- * furnished to do so, subject to the following conditions:
+ * SPDX-License-Identifier: MIT
  *
- * The above copyright notice and this permission notice shall be included in
- * all copies or substantial portions of the Software.
- *
- * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
- * IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
- * FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
- * AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
- * LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
- * OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
- * SOFTWARE.
+ * Copyright (C) 2010-2019 EfficiOS Inc. and Linux Foundation
  */
 
+#ifndef BABELTRACE2_TRACE_IR_STREAM_H
+#define BABELTRACE2_TRACE_IR_STREAM_H
+
 #ifndef __BT_IN_BABELTRACE_H
 # error "Please include <babeltrace2/babeltrace.h> instead."
 #endif
@@ -69,7 +53,7 @@ which can belong to different streams, as long as the stream clocks are
 \ref api-tir-clock-cls-origin "correlatable".
 
 A typical use case for streams is to use one for each traced CPU. Then
-the messages related to a given stream are the ones which occured on a
+the messages related to a given stream are the ones which occurred on a
 given CPU. Other schemes are possible: they are completely
 application-specific, and \bt_name does not enforce any specific
 stream arrangement pattern.
@@ -105,7 +89,7 @@ In the illustration above, notice that:
   stream's default clock.
 
   In other words, a default clock snapshot contains the value of the
-  stream's default clock when this message occured.
+  stream's default clock when this message occurred.
 
 To create a stream: