The config OMAP_INTERCONNECT that this driver depends on (in drivers/bus/Kconfig) is tristate. So it can be a module.
Also there are module related setup calls within this driver. Explicitly add module.h to includes so it won't be a build failure when future cleanups are integrated and the implicit presence of certain module prototypes disappears. Cc: Russell King <li...@arm.linux.org.uk> Cc: linux-arm-ker...@lists.infradead.org Signed-off-by: Paul Gortmaker <paul.gortma...@windriver.com> --- drivers/bus/omap_l3_smx.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/bus/omap_l3_smx.c b/drivers/bus/omap_l3_smx.c index acc2164..8a61433 100644 --- a/drivers/bus/omap_l3_smx.c +++ b/drivers/bus/omap_l3_smx.c @@ -23,6 +23,7 @@ */ #include <linux/kernel.h> +#include <linux/module.h> #include <linux/slab.h> #include <linux/platform_device.h> #include <linux/interrupt.h> -- 1.8.4.1 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
