From: sshtylyov@ru•mvista.com (Sergei Shtylyov)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v2 1/7] LPC32xx: clock.c: Missing header file
Date: Mon, 30 Jan 2012 20:56:44 +0300 [thread overview]
Message-ID: <4F26D9DC.2000008@ru.mvista.com> (raw)
In-Reply-To: <1327939327-7799-1-git-send-email-stigge@antcom.de>
Hello.
On 01/30/2012 07:02 PM, Roland Stigge wrote:
> This patch fixes the compiler warnings regarding the EXPORT_SYMBOL usage
> Signed-off-by: Roland Stigge<stigge@antcom•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/module.h>
Shouldn't <linux/export.h> be included instead nowadays?
WBR, Sergei
next prev parent reply other threads:[~2012-01-30 17:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-30 16:02 [PATCH v2 1/7] LPC32xx: clock.c: Missing header file Roland Stigge
2012-01-30 16:02 ` [PATCH v2 2/7] LPC32xx: clock.c: jiffies wrapping Roland Stigge
2012-01-31 10:24 ` Wolfram Sang
2012-01-30 16:02 ` [PATCH v2 3/7] LPC32xx: clock.c: Clock registration fixes Roland Stigge
2012-01-30 16:02 ` [PATCH v2 4/7] LPC32xx: clock.c: MMC update Roland Stigge
2012-01-30 16:02 ` [PATCH v2 5/7] LPC32xx: clock.c: warning fix Roland Stigge
2012-01-31 10:26 ` Wolfram Sang
2012-01-30 16:02 ` [PATCH v2 6/7] LPC32xx: clock.c: USB PLL fix Roland Stigge
2012-01-31 10:34 ` Wolfram Sang
2012-02-01 13:27 ` Roland Stigge
2012-02-02 16:49 ` Wolfram Sang
2012-02-02 19:20 ` Roland Stigge
2012-02-02 23:01 ` Wolfram Sang
2012-01-30 16:02 ` [PATCH v2 7/7] LPC32xx: clock.c: Fix mutex lock issues Roland Stigge
2012-01-31 10:27 ` Wolfram Sang
2012-01-30 17:56 ` Sergei Shtylyov [this message]
2012-01-31 10:22 ` [PATCH v2 1/7] LPC32xx: clock.c: Missing header file Wolfram Sang
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=4F26D9DC.2000008@ru.mvista.com \
--to=sshtylyov@ru$(echo .)mvista.com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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