From: Tony Lindgren <tony@atomide.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: 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: Mon, 7 Nov 2011 09:56:45 -0800 [thread overview]
Message-ID: <20111107175645.GU31337@atomide.com> (raw)
In-Reply-To: <20111107174645.GE15294@n2100.arm.linux.org.uk>
* Russell King - ARM Linux <linux@arm.linux.org.uk> [111107 09:12]:
> On Mon, Nov 07, 2011 at 09:26:00AM -0800, Tony Lindgren wrote:
> > * Russell King - ARM Linux <linux@arm.linux.org.uk> [111106 03:44]:
> > > Yet again I find that I'm having to email about crap on OMAP3.
> > >
> > > I'm getting really fed up with OMAP stuff which keeps breaking in
> > > idiotic ways - and the way there's fatal build errors at EVERY merge
> > > window. The OMAP workflow is totally broken. Something MUST change
> > > in the way the OMAP community works to stop the continual breakage
> > > at every single bloody merge window.
> >
> > Hmm he following fixes are queued elsewhere and now merged:
> >
> > omap_hsmmc: fix missing parenthesis in pr_info
> > PM / OPP: Fix build when CONFIG_PM_OPP is not set
> > net: Add back alignment for size for __alloc_skb
> >
> > Or have you seen some other build errors?
> >
> > FYI, now all the compile warnings are finally gone with what
> > I have in fixes branch.
>
> It was the errors in the "ARM: OMAP: Fix build for OMAP3 only builds"
> thread.
OK, that's queued up.
> However, rebuilding today gives brand new breakage - for my OMAP4430SDP
> config. This seems to be because more linux/module.h includes have been
> deleted from include/linux/*.h includes.
>
> arch/arm/plat-omap/dmtimer.c:184: warning: data definition has no type or storage class
...
Got a fix for that one queued up too.
> In addition, for OMAP3430 LDP:
>
> 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
Looks like there's a fix for this one posted, will add that.
> arch/arm/mach-omap2/mailbox.c:417: error: expected declaration specifiers or '...' before string constant
> arch/arm/mach-omap2/mailbox.c:417: warning: data definition has no type or storage class
> arch/arm/mach-omap2/mailbox.c:417: warning: type defaults to 'int' in declaration of 'MODULE_LICENSE'
...
> 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'
Yeah after pulling in the current mainline I see at least the above
two need to be patched.
> It might be an idea to do this:
>
> grep -rl EXPORT_SYMBOL arch/arm/*omap* | xargs grep -L linux/export.h
>
> and for any OMAP drivers as well. This gives:
>
> arch/arm/mach-omap1/id.c
> arch/arm/mach-omap1/lcd_dma.c
> arch/arm/mach-omap1/io.c
> arch/arm/mach-omap1/ams-delta-fiq.c
> arch/arm/mach-omap2/gpmc.c
> arch/arm/mach-omap2/id.c
> arch/arm/mach-omap2/io.c
> arch/arm/plat-omap/ocpi.c
> arch/arm/plat-omap/mcbsp.c
> arch/arm/plat-omap/omap_device.c
> arch/arm/plat-omap/mux.c
> arch/arm/plat-omap/devices.c
> arch/arm/plat-omap/io.c
> arch/arm/plat-omap/dma.c
> arch/arm/plat-omap/dmtimer.c
> arch/arm/plat-omap/mailbox.c
>
> which probably should all be fixed before any more of these errors
> spring up.
Except for the ones that have module.h included as that already
includes export.h. At least the dmtimer.c will be moved to drivers,
and could be a loadable module so module.h is better there.
Anyways, will check these and post patches.
Regards,
Tony
next prev parent reply other threads:[~2011-11-07 17:56 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 [this message]
2011-11-07 20:26 ` Tony Lindgren
2011-11-08 8:13 ` Tomi Valkeinen
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=20111107175645.GU31337@atomide.com \
--to=tony@atomide.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 \
/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