>> A recent change in kernel 3.2 ABI needs patching wireless
>> sources in order to compil. As F-15 seems to use kernel 3.x series
>> renamed with this motif 2.6.4x, I wanted to know if the future kernel
>> versions numbers for F-15 will keep this scheme? If I understood it
>> correctly, in this case next one will be 2.6.42.y-z (for 3.2) and will
>> be followed by 2.6.43.y-z (for 3.3) etc. Knowing this exactly will make
>> it easier to build the C preprocessor macro for the wireless kernel
>> modules sources patch for both F-15/F-16.
> Yes, when F15 is rebased to 3.2, it will be called 2.6.42 and 3.3
> would be 2.6.43.
Didn't Chuck change it so LINUX_VERSION_CODE always calls itself 3.x
now? If so, then you shouldn't need any cpp to consider 2.6.4x, as
that's only for the utsname.
If I understand correctly what you mean, this macro (on one line)
#if LINUX_VERSION_CODE >= KERNEL_VERSION(3, 2, 0) || (LINUX_VERSION_CODE
= KERNEL_VERSION(2, 6, 42) && LINUX_VERSION_CODE <
would be equivalent and have the same behavior of this one
#if LINUX_VERSION_CODE >= KERNEL_VERSION(3, 2, 0)
in F-15 as in F-16?