Pre-release kernel versioning?

[Michel Salim]

2007/3/18, KH KH <kwizart at gmail.com>:

> Well, i have the same problem some time ago with rt2x00 Ralink chipsets
>  (when it was not inside the kernel, mean since 2.6.21rc1 )
> I try to build some kmod
>  (review was here :
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=202528 - This is
> planned to be closed when 2.6.21 will be stable...)
> It was working fine with each 2.6.19 release but not for 2.6.20-1.2925.fc6
> See here: http://rt2x00.serialmonkey.com/phpBB2/viewtopic.php?p=20463#20463
> There is a problem with the rfkill part...I din't dig more for now...
> I'm surprised that another driver have the same issue, i've thought
> this was happenning only with rt2x00. Developpers of this module don't
> support fedora build error for this reason...
>

Generally the fix is quite trivial: if the kernel module supports
several different kernels, find the place where it probes what kernel
it's being built against and change references to the upstream kernel
version (in this case 2.6.21) to 2.6.20, which is what your kernel is
reporting.

It's just a bit annoying to have to do it each time, since I'd have to
delete the modified file everytime it's modified upstream, get the
newer version and then re-modify it.

Regards,

-- 
Michel Salim
http://hircus.wordpress.com/

My theology, briefly, is that the universe was dictated but not signed.
                -- Christopher Morley