* 2.6.11.x, EXTRAVERSION and module compatibility
@ 2005-03-16 16:48 Michael Tokarev
2005-03-16 17:00 ` Arjan van de Ven
0 siblings, 1 reply; 2+ messages in thread
From: Michael Tokarev @ 2005-03-16 16:48 UTC (permalink / raw)
To: Kernel Mailing List
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2005-03-16 17:00 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-03-16 16:48 2.6.11.x, EXTRAVERSION and module compatibility Michael Tokarev
2005-03-16 17:00 ` Arjan van de Ven
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.