X-Git-Url: http://git.liburcu.org/?a=blobdiff_plain;f=doc%2Fdeveloper%2Flttng-lttv-compatibility.html;h=ab4cb738d4435d80576667b54a91ddd13f0c8bf0;hb=2cd021e04d88e9fabaab1d442be30642ec1fc971;hp=c1795a5403e8fbf39c8b6fbbcf1aedce19e34b90;hpb=4e0b958a111ac9e006acd135a6c8a97f8a959bf6;p=lttv.git

diff --git a/doc/developer/lttng-lttv-compatibility.html b/doc/developer/lttng-lttv-compatibility.html
index c1795a54..ab4cb738 100644
--- a/doc/developer/lttng-lttv-compatibility.html
+++ b/doc/developer/lttng-lttv-compatibility.html
@@ -3843,6 +3843,7 @@ powerpc64, s390, sparc, sparc64.<br>
 0.219<br>
 0.220<br>
 0.221<br>
+0.222<br>
 </td>
 <td style="vertical-align: top;">
 0.76<br>
@@ -3879,6 +3880,7 @@ obsolete<br>
 2.6.33.3<br>
 2.6.33.4<br>
 2.6.34<br>
+2.6.34.4<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
@@ -3961,9 +3963,10 @@ compilers.<br>
 LTTV 0.12.34 fixes a bug in string handling in libltttraceread. Caused incorrect
 string length calculation when a string appeared in many per-cpu tracefiles of
 the same channel.<br>
-LTTng 0.221 is now supports writing strings into the buffer when string input is
+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.<br>
 </td>
 <td style="vertical-align: top;">
 </td>