From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Russell King <linux@arm.linux.org.uk>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
Paul Gortmaker <paul.gortmaker@windriver.com>
Subject: [PATCH 2/3] arm: include module.h in drivers/bus/omap_l3_smx.c
Date: Mon, 13 Jan 2014 19:19:42 -0500 [thread overview]
Message-ID: <1389658783-9876-3-git-send-email-paul.gortmaker@windriver.com> (raw)
In-Reply-To: <1389658783-9876-1-git-send-email-paul.gortmaker@windriver.com>
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.
Signed-off-by: Paul Gortmaker <paul.gortmaker@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 acc216491b8a..8a614332dcb9 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.5.2
next prev parent reply other threads:[~2014-01-14 0:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-14 0:19 [PATCH 0/3] arm: remap non-modular uses of module_init properly Paul Gortmaker
2014-01-14 0:19 ` [PATCH 1/3] arm: use subsys_initcall in non-modular pl320 IPC code Paul Gortmaker
2014-01-14 0:19 ` Paul Gortmaker [this message]
2014-01-14 0:19 ` [PATCH 3/3] arm: don't use module_init in non-modular mach-vexpress/spc.c code Paul Gortmaker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1389658783-9876-3-git-send-email-paul.gortmaker@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome