From: khilman@linaro.org (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: OMAP2+: SmartReflex: soc.h is needed for omap initcalls
Date: Tue, 12 Feb 2013 14:23:56 -0800 [thread overview]
Message-ID: <1360707836-2545-1-git-send-email-khilman@linaro.org> (raw)
commit aa4f99638b (ARM: OMAP2+: Use omap initcalls) converted
the initcalls here, but did not #include "soc.h" where the omap
inicalls are defined.
To fix, #include <soc.h>
Signed-off-by: Kevin Hilman <khilman@linaro.org>
---
Tony, the patch that broke this was introduced in your
omap-for-v3.9/multiplatform-enable-signed branch, and this problem was
found only when compiling with PM (specifically, SmartReflex) enabled.
arch/arm/mach-omap2/smartreflex-class3.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/mach-omap2/smartreflex-class3.c b/arch/arm/mach-omap2/smartreflex-class3.c
index 80f3acb..b2dcbd3 100644
--- a/arch/arm/mach-omap2/smartreflex-class3.c
+++ b/arch/arm/mach-omap2/smartreflex-class3.c
@@ -13,6 +13,7 @@
#include <linux/power/smartreflex.h>
#include "voltage.h"
+#include "soc.h"
static int sr_class3_enable(struct omap_sr *sr)
{
--
1.8.1.2
next reply other threads:[~2013-02-12 22:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-12 22:23 Kevin Hilman [this message]
2013-02-13 1:12 ` [PATCH] ARM: OMAP2+: SmartReflex: soc.h is needed for omap initcalls Tony Lindgren
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=1360707836-2545-1-git-send-email-khilman@linaro.org \
--to=khilman@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).