From: stigge@antcom.de
To: w.sang@pengutronix.de, bangaragiri.g@nxp.com,
srinivas.bakki@nxp.com, sundarapandian.andithevar@nxp.com,
linus.walleij@linaro.org, linux-kernel@vger.kernel.org,
kevin.wells@nxp.com, linux-arm-kernel@lists.infradead.org
Cc: Roland Stigge <stigge@antcom.de>
Subject: [PATCH v3 3/7] ARM: LPC32xx: clock.c: Missing header file
Date: Thu, 2 Feb 2012 20:19:44 +0100 [thread overview]
Message-ID: <1328210388-21296-3-git-send-email-stigge@antcom.de> (raw)
In-Reply-To: <1328210388-21296-1-git-send-email-stigge@antcom.de>
This patch fixes the compiler warnings regarding the EXPORT_SYMBOL usage
Signed-off-by: Roland Stigge <stigge@antcom.de>
Acked-by: Wolfram Sang <w.sang@pengutronix.de>
diff --git a/arch/arm/mach-lpc32xx/clock.c b/arch/arm/mach-lpc32xx/clock.c
index 1e02751..8e79313 100644
--- a/arch/arm/mach-lpc32xx/clock.c
+++ b/arch/arm/mach-lpc32xx/clock.c
@@ -82,6 +82,7 @@
* will also impact the individual peripheral rates.
*/
+#include <linux/export.h>
#include <linux/kernel.h>
#include <linux/list.h>
#include <linux/errno.h>
next prev parent reply other threads:[~2012-02-02 19:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-02 19:19 [PATCH v3 1/7] ARM: LPC32xx: Added lpc32xx_defconfig stigge
2012-02-02 19:19 ` [PATCH v3 2/7] ARM: LPC32XX: Remove broken non-static declaration stigge
2012-02-02 19:19 ` stigge [this message]
2012-02-02 19:19 ` [PATCH v3 4/7] ARM: LPC32xx: clock.c: jiffies wrapping stigge
2012-02-02 19:19 ` [PATCH v3 5/7] ARM: LPC32xx: clock.c: Clock registration fixes stigge
2012-02-02 19:19 ` [PATCH v3 6/7] ARM: LPC32xx: clock.c: warning fix stigge
2012-02-02 19:19 ` [PATCH v3 7/7] ARM: LPC32xx: clock.c: Fix mutex lock issues stigge
2012-02-02 21:23 ` [PATCH v3 1/7] ARM: LPC32xx: Added lpc32xx_defconfig Wolfram Sang
2012-02-02 21:52 ` Kevin Wells
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=1328210388-21296-3-git-send-email-stigge@antcom.de \
--to=stigge@antcom.de \
--cc=bangaragiri.g@nxp.com \
--cc=kevin.wells@nxp.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=srinivas.bakki@nxp.com \
--cc=sundarapandian.andithevar@nxp.com \
--cc=w.sang@pengutronix.de \
/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
all inboxes | Powered by JetHome®