From: Tony Lindgren <tony@atomide.com>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: linux-omap@vger.kernel.org,
Russell King - ARM Linux <linux@arm.linux.org.uk>
Subject: Re: More randconfig OMAP build errors
Date: Tue, 28 Feb 2012 14:46:23 -0800 [thread overview]
Message-ID: <20120228224623.GG18901@atomide.com> (raw)
In-Reply-To: <20120228102229.GE18045@n2100.arm.linux.org.uk>
Tomi,
* Russell King - ARM Linux <linux@arm.linux.org.uk> [120228 01:50]:
> Todays randconfig found this:
>
> drivers/video/omap2/displays/panel-dvi.c: In function 'panel_dvi_ddc_read':
> drivers/video/omap2/displays/panel-dvi.c:239: error: implicit declaration of function 'i2c_transfer'
> drivers/video/omap2/displays/panel-dvi.c: In function 'panel_dvi_read_edid':
> drivers/video/omap2/displays/panel-dvi.c:265: error: implicit declaration of function 'i2c_get_adapter'
>
> caused by I2C being disabled.
>
> There's also some warnings in arch/arm/mach-omap2/omap_l3_smx.c and
> drivers/video/omap2/dss/apply.c about unused variables:
>
> arch/arm/mach-omap2/omap_l3_smx.c: In function 'omap3_l3_block_irq':
> arch/arm/mach-omap2/omap_l3_smx.c:156: warning: unused variable 'address'
> arch/arm/mach-omap2/omap_l3_smx.c:155: warning: unused variable 'multi'
> arch/arm/mach-omap2/omap_l3_smx.c:154: warning: unused variable 'initid'
> arch/arm/mach-omap2/omap_l3_smx.c:153: warning: unused variable 'code'
> arch/arm/mach-omap2/omap_l3_smx.c: At top level:
> arch/arm/mach-omap2/omap_l3_smx.c:68: warning: 'omap3_l3_code_string' defined but not used
> arch/arm/mach-omap2/omap_l3_smx.c:90: warning: 'omap3_l3_initiator_string' defined but not used
> drivers/video/omap2/dss/apply.c:350: warning: 'wait_pending_extra_info_updates' defined but not used
Care to take a look at fixing the above?
Tony
next prev parent reply other threads:[~2012-02-28 22:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 10:22 More randconfig OMAP build errors Russell King - ARM Linux
2012-02-28 22:46 ` Tony Lindgren [this message]
2012-02-29 8:50 ` 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=20120228224623.GG18901@atomide.com \
--to=tony@atomide.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=tomi.valkeinen@ti.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;
as well as URLs for NNTP newsgroup(s).