| |||||||||||||
The conclusion of the 3.9 merge windowThe conclusion of the 3.9 merge windowPosted Mar 6, 2013 6:08 UTC (Wed) by bergwolf (subscriber, #55931)Parent article: The conclusion of the 3.9 merge window
> The hlist_for_each_entry() iterator has lost the unused "pos" parameter.
Yet another nightmare for out-of-tree modules that aim at supporting multiple kernel versions. sigh...
(Log in to post comments)
The conclusion of the 3.9 merge window Posted Mar 6, 2013 8:43 UTC (Wed) by renox (subscriber, #23785) [Link]
>> The hlist_for_each_entry() iterator has lost the unused "pos" parameter.
>Yet another nightmare for out-of-tree modules that aim at supporting multiple kernel versions. sigh...
And a perfect example why the kernel doesn't keep a stable internal ABI: otherwise you have to keep unused parameters aka bloat.
The conclusion of the 3.9 merge window Posted Mar 6, 2013 18:02 UTC (Wed) by marduk (subscriber, #3831) [Link]
>> The hlist_for_each_entry() iterator has lost the unused "pos" parameter.
Unused parameters are undesirable.
>Yet another nightmare for out-of-tree modules that aim at supporting multiple kernel versions. sigh...
Out-of-tree modules are undesirable.
The conclusion of the 3.9 merge window Posted Mar 6, 2013 22:04 UTC (Wed) by ovitters (subscriber, #27950) [Link]
If the module is added to the kernel the porting will be done for you. Plus the various kernel versions automatically will either have or won't have that parameter.
Or in other words: pretty well known that there is no stability guarantee and the developers prefer to include your module/driver in the kernel. Seems that this often also gets you a good review (thus better quality).
|
|||||||||||||