Message-ID: <42386368.5030604@tls.msk.ru>
Date: Wed, 16 Mar 2005 19:48:40 +0300
From: Michael Tokarev <mjt@tls.msk.ru>
User-Agent: Debian Thunderbird 1.0 (X11/20050116)
MIME-Version: 1.0
To: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: 2.6.11.x, EXTRAVERSION and module compatibility
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 877
Lines: 23

As far as I can see, the "super-stable" kernel releases
should not affect module ABI in any way, that is, a module
compiled for 2.6.11 or 2.6.11.2 should work with 2.6.11.4
and vise versa.  Ofcourse I'm talking about modules which
are out of the main kernel tree.

But.  EXTRAVERSION gets changed with every 2.6.11.x release,
thus making out-of-tree modules incompatible just because
they contain different kernel version tag.

The question is obvious: Is this a correct/intended behaviour?
Maybe, just maybe, EXTRAVERSION should not be taken into
account when desciding if a given module compiled for a
given kernel?

Thanks.

/mjt
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/