it occurred to me as i was perusing some of the source files that some of those files were including module.h for no other reason than to have access to the EXPORT_* macros. but why are those macros in module.h?
they're not tied specifically to modules. for example, the file kernel/mutex.c can't possibly be selected to be a module, and yet it has to include that header file. wouldn't it make more sense to have the EXPORT and symbol stuff in, perhaps, kernel.h? or some other, lower-level header file that would remove the need for including module.h in a file that has absolutely nothing to do with modules? rday -- ======================================================================== Robert P. J. Day Linux Consulting, Training and Annoying Kernel Pedantry Waterloo, Ontario, CANADA http://crashcourse.ca ======================================================================== -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to [EMAIL PROTECTED] Please read the FAQ at http://kernelnewbies.org/FAQ
