Pre-release kernel versioning?

[KH KH]

2007/3/18, Michel Salim <michel.salim at gmail.com>:
> Hi,
>
> Currently each Rawhide pre-release kernel reports as its version
> number the version number of the previous stable version, rather than
> the current version.
>
> This sometimes causes problems with out-of-kernel modules (e.g. with
> madwifi), since the exposed kernel API has changed and the #ifdef's
> normally checks for the new version.
>
> Since the typical end-user on a stable Fedora release will never see
> these pre-release kernels, what would be the downside of, say, calling
> the current kernel 2.6.21-0.2997.fc7 rather than 2.6.20-1.2997.fc7 ?
>
> Thanks,
>
> --
> Michel Salim
> http://hircus.wordpress.com/
>
> --
> fedora-devel-list mailing list
> fedora-devel-list at redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-devel-list
>
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...

Nicolas (kwizart)