On Sat, 28 Oct 2000 11:02:04 +0100 (BST), 
Alan Cox <[EMAIL PROTECTED]> wrote:
>> of get_module_symbol this weekend.  The inter-object registration code
>> will allow two objects to pass data to each other, it will not matter
>> whether the objects are both modules, one module and one built in (in
>> either order) or both built in.  When modules are involved there will
>> be full module locking.
>Dont forget that one of the objects may not even be present, or may be
>loaded later.

How could I forget it?  You have defined the heart of the problem,
either object might be built into the kernel, might be a module or
might not even be there, in any case the load order is undefined.  That
is why existing code is kludging things by using get_module_symbol().
inter_module_register, unregister, get, put will solve the inter object
problem but using a clean interface that works with symbol versions.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/

Reply via email to