From d5199b01cc9a845a021b302fe2fb5ba03f4fc417 Mon Sep 17 00:00:00 2001
From: compudj <compudj@04897980-b3bd-0310-b5e0-8ef037075253>
Date: Wed, 10 Jun 2009 17:03:55 +0000
Subject: [PATCH] update compat

git-svn-id: http://ltt.polymtl.ca/svn@3400 04897980-b3bd-0310-b5e0-8ef037075253
---
 trunk/lttv/doc/developer/lttng-lttv-compatibility.html | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/trunk/lttv/doc/developer/lttng-lttv-compatibility.html b/trunk/lttv/doc/developer/lttng-lttv-compatibility.html
index 552c0d4d..05252f85 100644
--- a/trunk/lttv/doc/developer/lttng-lttv-compatibility.html
+++ b/trunk/lttv/doc/developer/lttng-lttv-compatibility.html
@@ -3429,6 +3429,7 @@ powerpc64, s390, sparc, sparc64.<br>
 0.137<br>
 0.138<br>
 0.139<br>
+0.140<br>
 </td>
 <td style="vertical-align: top;">
 0.65<br>
@@ -3457,6 +3458,7 @@ obsolete<br>
 2.6.30-rc1<br>
 2.6.30-rc2<br>
 2.6.30-rc5<br>
+2.6.30<br>
 </td>
 <td style="vertical-align: top;">
 LTTng 0.92 reorders the LTTng patchset and drops the /proc/ltt interface.<br>
@@ -3507,6 +3509,7 @@ a good deal of paranoia : don't trust the Linux IPI mechanism to ensure that
 memory is presented in program order when the remote ipi handler runs. Use our
 own smp_mb()s to ensure memory ordering. It's a slow path anyway, we don't
 care.<br>
+LTTng 0.140 supports kernel 2.6.30.<br>
 </td>
 <td style="vertical-align: top;">
 </td>
-- 
2.34.1