> a better way would be then to have a "core" module which is basically
> collecting these algorithms, and then have the algorithm modules, when
> they are loaded, register themselves with this core module. (and
> unregister at unload). It's sort of inside-out with they way you're
> trying to do it, but it'll work out a lot nicer. Obviously the user of
> the algorithms can be another module in addition to this core module.
> (and even register algorithms itself)
Exactly, I agree 100%. But here's the catch: it's not an option at this
point in time. What I described earlier is what I currently need to do.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
