update compat

[lttv.git] / doc / developer / lttng-lttv-compatibility.html

diff --git a/doc/developer/lttng-lttv-compatibility.html b/doc/developer/lttng-lttv-compatibility.html
index 8f87b2d2c602c1eea361466957cece8e0208f58e..2de0c57040877b6b108fe400282526f85f2ab3a8 100644 (file)
--- a/doc/developer/lttng-lttv-compatibility.html
+++ b/doc/developer/lttng-lttv-compatibility.html
@@ -3810,6 +3810,7 @@ powerpc64, s390, sparc, sparc64.<br>
 0.12.32<br>
 0.12.33<br>
 0.12.34<br>
+0.12.35<br>
 </td>
 <td style="vertical-align: top;">
 0.191<br>
@@ -3843,6 +3844,9 @@ powerpc64, s390, sparc, sparc64.<br>
 0.219<br>
 0.220<br>
 0.221<br>
+0.222<br>
+0.223<br>
+0.224<br>
 </td>
 <td style="vertical-align: top;">
 0.76<br>
@@ -3879,6 +3883,8 @@ obsolete<br>
 2.6.33.3<br>
 2.6.33.4<br>
 2.6.34<br>
+2.6.34.4<br>
+2.6.35.2<br>
 </td>
 <td style="vertical-align: top;">
 LTTng 0.191, LTTV 0.12.30 coming with trace format 2.6 revert to the pre-2.4
@@ -3964,6 +3970,15 @@ the same channel.<br>
 LTTng 0.221 now supports writing strings into the buffer when string input is
 being modified concurrently. Such a race should not render the trace
 unreadable.<br>
+LTTng 0.222 supports kernel 2.6.34.4. It includes a lttng splice actor
+adjustment to match a splice.c change in 2.6.34.2 which changed the checks for
+seekable files.<br>
+LTTV 0.12.35 fixes a problem introduced in 0.12.34, fixing the problem initially
+fixed by 0.12.34 in the "correct" way; without unwanted side-effects. LTTV
+0.12.34 had problems calling hooks for some events.<br>
+LTTng 0.223 supports kernel 2.6.35.2.<br>
+LTTng 0.224 fixes socket instrumentation in git tree: the patch hunk management
+differs between quilt and git, so only the git tree showed this problem.<br>
 </td>
 <td style="vertical-align: top;">
 </td>