> cc list trimmed.  Nobody has come up with a "must have" reason for
> get_module_symbol and that interface is broken as designed.  I will be

Nobody has come up with a 'must break existing sane code' reason either.

> 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.

You have no consensus on this. None at all. It is also past the 2.4test
point for making this change.


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