From: khilman@ti.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RESEND] ARM: OMAP: omap_device: Include linux/export.h
Date: Thu, 03 Nov 2011 07:26:57 -0700 [thread overview]
Message-ID: <87d3d9i8ni.fsf@ti.com> (raw)
In-Reply-To: <1320303638.17983.5.camel@phoenix> (Axel Lin's message of "Thu, 03 Nov 2011 15:00:38 +0800")
Axel Lin <axel.lin@gmail.com> writes:
> Include linux/export.h to fix below build warning:
>
> CC arch/arm/plat-omap/omap_device.o
> arch/arm/plat-omap/omap_device.c:1055: warning: data definition has no type or storage class
> arch/arm/plat-omap/omap_device.c:1055: warning: type defaults to 'int' in declaration of 'EXPORT_SYMBOL'
> arch/arm/plat-omap/omap_device.c:1055: warning: parameter names (without types) in function declaration
>
> Signed-off-by: Axel Lin <axel.lin@gmail.com>
Thanks, will queue as a fix for v3.2-rc
Kevin
next prev parent reply other threads:[~2011-11-03 14:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-03 7:00 [PATCH RESEND] ARM: OMAP: omap_device: Include linux/export.h Axel Lin
2011-11-03 14:26 ` Kevin Hilman [this message]
2011-11-03 14:47 ` Paul Gortmaker
2011-11-03 17:48 ` Kevin Hilman
2011-11-07 20:35 ` 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=87d3d9i8ni.fsf@ti.com \
--to=khilman@ti.com \
--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).