From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Per Forlin <per.forlin@linaro.org>, Chris Ball <cjb@laptop.org>,
Felipe Balbi <balbi@ti.com>
Subject: Re: OMAP CRAP: The Continuing Story Of Brokenness
Date: Tue, 08 Nov 2011 10:13:12 +0200 [thread overview]
Message-ID: <1320739992.1907.34.camel@deskari> (raw)
In-Reply-To: <20111107202620.GW31337@atomide.com>
[-- Attachment #1: Type: text/plain, Size: 2052 bytes --]
Hi Tony,
On Mon, 2011-11-07 at 12:26 -0800, Tony Lindgren wrote:
> Tomi,
>
> * Russell King - ARM Linux <linux@arm.linux.org.uk> [111107 09:12]:
>
> > drivers/video/omap/dispc.c:276: warning: data definition has no type or storage class
> > drivers/video/omap/dispc.c:276: warning: type defaults to 'int' in declaration of 'EXPORT_SYMBOL'
> > drivers/video/omap/dispc.c:276: warning: parameter names (without types) in function declaration
> > drivers/video/omap/dispc.c:286: warning: data definition has no type or storage class
> > drivers/video/omap/dispc.c:286: warning: type defaults to 'int' in declaration of 'EXPORT_SYMBOL'
> > drivers/video/omap/dispc.c:286: warning: parameter names (without types) in function declaration
> > drivers/video/omap/dispc.c:320: warning: data definition has no type or storage class
> > drivers/video/omap/dispc.c:320: warning: type defaults to 'int' in declaration of 'EXPORT_SYMBOL'
> > drivers/video/omap/dispc.c:320: warning: parameter names (without types) in function declaration
> > drivers/video/omap/dispc.c:328: warning: data definition has no type or storage class
> > drivers/video/omap/dispc.c:328: warning: type defaults to 'int' in declaration of 'EXPORT_SYMBOL'
> > drivers/video/omap/dispc.c:328: warning: parameter names (without types) in function declaration
> > drivers/video/omap/dispc.c:863: warning: data definition has no type or storage class
> > drivers/video/omap/dispc.c:863: warning: type defaults to 'int' in declaration of 'EXPORT_SYMBOL'
> > drivers/video/omap/dispc.c:863: warning: parameter names (without types) in function declaration
> > drivers/video/omap/dispc.c:883: warning: data definition has no type or storage class
> > drivers/video/omap/dispc.c:883: warning: type defaults to 'int' in declaration of 'EXPORT_SYMBOL'
> > drivers/video/omap/dispc.c:883: warning: parameter names (without types) in function declaration
>
> Care to queue something for drivers/video/omap warnings above?
Sure, I'll send a patch for -rc2.
Tomi
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2011-11-08 8:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-06 12:18 OMAP CRAP: The Continuing Story Of Brokenness Russell King - ARM Linux
2011-11-06 13:06 ` S, Venkatraman
2011-11-06 15:29 ` Per Förlin
2011-11-07 17:26 ` Tony Lindgren
2011-11-07 17:46 ` Russell King - ARM Linux
2011-11-07 17:56 ` Tony Lindgren
2011-11-07 20:26 ` Tony Lindgren
2011-11-08 8:13 ` Tomi Valkeinen [this message]
2011-11-07 17:51 ` Felipe Balbi
2011-11-07 17:30 ` S, Venkatraman
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=1320739992.1907.34.camel@deskari \
--to=tomi.valkeinen@ti.com \
--cc=balbi@ti.com \
--cc=cjb@laptop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=per.forlin@linaro.org \
--cc=tony@atomide.com \
/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