Hi!
> Pavel> 2.2.X compatibility should be stripped from maestro, and then
> Pavel> yes, module_init() would be the right way to go, along with
> Pavel> module_exit. But just now...
>
> Why?
> Some of us are trying to maintain drivers that are being used both in
> 2.2.x and 2.3.x - having the compatibillity code stripped out
> regularly from someone making a quick hack in the 2.3.x tree is a
> major pain.
I do not want to make it painy for maintainer, that means that I stick
to minimal solution (__initcall), instead of proper solution (put
module_init() + module_exit() there; but that would probably mean that
backward compatibility glue would go, or I would have to develop glue
for module_init().)
Pavel
-- The best software in life is free (not shareware)! Pavel GCM d? s-: !g p?:+ au- a--@ w+ v- C++@ UL+++ L++ N++ E++ W--- M- Y- R+- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Apr 23 2000 - 21:00:10 EST