> The only thing that was not clear to me from reviewing the module > namespace stuff a while ago was the original intent, but I confess I > actually only looked at the technical details to see if it was > applicable to the backports case, do you recall the original > motivation ? The original intent was to provide a cleaner export symbol API. There are roughly two classes of exported symbols: - Generally usable, well designed, interfaces intended to be used by multiple modules (e.g. functions for drivers to register themselves or library functions) - Special purpose exports that are only really for a single module, but are not intended as a general interface. These interfaces are usually not really clean and reusable. The idea was to mark the later special purpose exports with the name of the module that is supposed to them. They wouldn't be available to everybody else and wouldn't become part of the general kernel module API. -Andi -- To unsubscribe from this list: send the line "unsubscribe backports" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
