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
Subject: Re: Broken builds
Date: Tue, 05 Jun 2012 16:20:00 +0300 [thread overview]
Message-ID: <1338902400.1952.19.camel@lappyti> (raw)
In-Reply-To: <20120605082218.GL12766@atomide.com>
[-- Attachment #1: Type: text/plain, Size: 853 bytes --]
Hi,
On Tue, 2012-06-05 at 01:22 -0700, Tony Lindgren wrote:
> * Russell King - ARM Linux <linux@arm.linux.org.uk> [120603 11:05]:
> > Looks like the DSS stuff has broken OMAP builds again during this
> > merge window:
> >
> > drivers/video/omap2/dss/core.c:197: error: static declaration of 'dss_debugfs_create_file' follows non-static declaration
> > drivers/video/omap2/dss/dss.h:166: error: previous declaration of 'dss_debugfs_create_file' was here
> >
> > Both the OMAP3 and OMAP4 builds break with these two errors.
>
> Here's a patch for Tomi to fix this one.
I have a patch for this in my for-rc branch. It just missed the main
merge. I'll send this and a few other fixes today for the next rc.
Btw, it compiles if you have debugfs and DSS_DEBUG_SUPPORT enabled.
That's why I didn't notice it until too late.
Tomi
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-06-05 13:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-03 18:01 Broken builds Russell King - ARM Linux
2012-06-05 8:22 ` Tony Lindgren
2012-06-05 13:20 ` Tomi Valkeinen [this message]
2012-06-06 7:58 ` Tony Lindgren
2012-06-11 16:09 ` Russell King - ARM Linux
2012-06-11 17:12 ` Tomi Valkeinen
2012-06-11 16:06 ` Russell King - ARM Linux
2012-06-11 16:59 ` Tomi Valkeinen
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=1338902400.1952.19.camel@lappyti \
--to=tomi.valkeinen@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--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