Driver core: move the driver specific module code into the driver core
authorGreg Kroah-Hartman <gregkh@suse.de>
Wed, 28 Nov 2007 20:23:18 +0000 (12:23 -0800)
committerGreg Kroah-Hartman <gregkh@suse.de>
Fri, 25 Jan 2008 04:40:35 +0000 (20:40 -0800)
commitc63469a3985a9771c18a916b8d42845d044ea0b1
tree7d54c8741aec9d71864203ce430d289d40c4c975
parentcbe9c595f1de2e2a98403be2c14bfbc2486e84c4
Driver core: move the driver specific module code into the driver core

The module driver specific code should belong in the driver core, not in
the kernel/ directory.  So move this code.  This is done in preparation
for some struct device_driver rework that should be confined to the
driver core code only.

This also lets us keep from exporting these functions, as no external
code should ever be calling it.

Thanks to Andrew Morton for the !CONFIG_MODULES fix.

Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
drivers/base/Makefile
drivers/base/base.h
drivers/base/module.c [new file with mode: 0644]
include/linux/module.h
kernel/module.c