From: Jon Hunter <jon-hunter@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
Eduardo Valentin <eduardo.valentin@ti.com>,
Radhesh Fadnis <radhesh.fadnis@ti.com>
Subject: Re: OMAP* Latest build failures
Date: Tue, 20 Nov 2012 17:00:19 -0600 [thread overview]
Message-ID: <50AC0B83.9070704@ti.com> (raw)
In-Reply-To: <20121120175733.GH18567@atomide.com>
On 11/20/2012 11:57 AM, Tony Lindgren wrote:
> * Russell King - ARM Linux <linux@arm.linux.org.uk> [121117 01:35]:
>> On Wed, Nov 14, 2012 at 09:26:43AM +0000, Russell King - ARM Linux wrote:
>>> OMAP* allnoconfig fails:
>>>
>>> arch/arm/mach-omap2/built-in.o: In function `omap_dss_set_min_bus_tput':
>>> twl-common.c:(.text+0x1e08): undefined reference to `omap_pm_set_min_bus_tput'
>>> arch/arm/mach-omap2/built-in.o: In function `omap_hwmod_init_postsetup':
>>> twl-common.c:(.init.text+0x8f8): undefined reference to `omap_pm_if_early_init'
>>> arch/arm/mach-omap2/built-in.o: In function `omap_serial_init_port':
>>> twl-common.c:(.init.text+0x1284): undefined reference to `omap_pm_get_dev_context_loss_count'
>>> arch/arm/mach-omap2/built-in.o: In function `omap_timer_init':
>>> twl-common.c:(.init.text+0x1544): undefined reference to `omap_pm_get_dev_context_loss_count'
>>> arch/arm/mach-omap2/built-in.o: In function `omap2_common_pm_init':
>>> twl-common.c:(.init.text+0x1af0): undefined reference to `omap_pm_if_init'
>>> arch/arm/mach-omap2/built-in.o: In function `omap2_gpio_dev_init':
>>> twl-common.c:(.init.text+0x2168): undefined reference to `omap_pm_get_dev_context_loss_count'
>>> arch/arm/mach-omap2/built-in.o: In function `omap_display_init':
>>> twl-common.c:(.init.text+0x25cc): undefined reference to `omap_pm_get_dev_context_loss_count'
>>
>> These are now gone, but we have a new warning:
>>
>> arch/arm/mach-omap2/timer.c:163:28: warning: 'omap_counter_match' defined but not used
>
> Jon, care to fix this one?
Fix already available here [1]. I actually included this in my latest
pull request with some other timer clean-ups [2]. Let me know if you are
ok with this being part of this pull request or if you want to handle
this separately.
Cheers
Jon
[1] http://marc.info/?l=linux-omap&m=135300866115036&w=2
[2] http://marc.info/?l=linux-omap&m=135308624321232&w=2
WARNING: multiple messages have this Message-ID (diff)
From: jon-hunter@ti.com (Jon Hunter)
To: linux-arm-kernel@lists.infradead.org
Subject: OMAP* Latest build failures
Date: Tue, 20 Nov 2012 17:00:19 -0600 [thread overview]
Message-ID: <50AC0B83.9070704@ti.com> (raw)
In-Reply-To: <20121120175733.GH18567@atomide.com>
On 11/20/2012 11:57 AM, Tony Lindgren wrote:
> * Russell King - ARM Linux <linux@arm.linux.org.uk> [121117 01:35]:
>> On Wed, Nov 14, 2012 at 09:26:43AM +0000, Russell King - ARM Linux wrote:
>>> OMAP* allnoconfig fails:
>>>
>>> arch/arm/mach-omap2/built-in.o: In function `omap_dss_set_min_bus_tput':
>>> twl-common.c:(.text+0x1e08): undefined reference to `omap_pm_set_min_bus_tput'
>>> arch/arm/mach-omap2/built-in.o: In function `omap_hwmod_init_postsetup':
>>> twl-common.c:(.init.text+0x8f8): undefined reference to `omap_pm_if_early_init'
>>> arch/arm/mach-omap2/built-in.o: In function `omap_serial_init_port':
>>> twl-common.c:(.init.text+0x1284): undefined reference to `omap_pm_get_dev_context_loss_count'
>>> arch/arm/mach-omap2/built-in.o: In function `omap_timer_init':
>>> twl-common.c:(.init.text+0x1544): undefined reference to `omap_pm_get_dev_context_loss_count'
>>> arch/arm/mach-omap2/built-in.o: In function `omap2_common_pm_init':
>>> twl-common.c:(.init.text+0x1af0): undefined reference to `omap_pm_if_init'
>>> arch/arm/mach-omap2/built-in.o: In function `omap2_gpio_dev_init':
>>> twl-common.c:(.init.text+0x2168): undefined reference to `omap_pm_get_dev_context_loss_count'
>>> arch/arm/mach-omap2/built-in.o: In function `omap_display_init':
>>> twl-common.c:(.init.text+0x25cc): undefined reference to `omap_pm_get_dev_context_loss_count'
>>
>> These are now gone, but we have a new warning:
>>
>> arch/arm/mach-omap2/timer.c:163:28: warning: 'omap_counter_match' defined but not used
>
> Jon, care to fix this one?
Fix already available here [1]. I actually included this in my latest
pull request with some other timer clean-ups [2]. Let me know if you are
ok with this being part of this pull request or if you want to handle
this separately.
Cheers
Jon
[1] http://marc.info/?l=linux-omap&m=135300866115036&w=2
[2] http://marc.info/?l=linux-omap&m=135308624321232&w=2
next prev parent reply other threads:[~2012-11-20 23:00 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-14 9:26 OMAP* Latest build failures Russell King - ARM Linux
2012-11-14 9:26 ` Russell King - ARM Linux
2012-11-14 10:08 ` Peter Ujfalusi
2012-11-14 10:08 ` Peter Ujfalusi
2012-11-14 10:35 ` Russell King - ARM Linux
2012-11-14 10:35 ` Russell King - ARM Linux
2012-11-14 11:45 ` Tomi Valkeinen
2012-11-14 11:45 ` Tomi Valkeinen
2012-11-14 16:48 ` Tony Lindgren
2012-11-14 16:48 ` Tony Lindgren
2012-11-14 16:59 ` Tony Lindgren
2012-11-14 16:59 ` Tony Lindgren
2012-11-14 17:17 ` Tony Lindgren
2012-11-14 17:17 ` Tony Lindgren
2012-11-14 17:44 ` Russell King - ARM Linux
2012-11-14 17:44 ` Russell King - ARM Linux
2012-11-14 17:42 ` Russell King - ARM Linux
2012-11-14 17:42 ` Russell King - ARM Linux
2012-11-17 9:33 ` Russell King - ARM Linux
2012-11-17 9:33 ` Russell King - ARM Linux
2012-11-20 17:57 ` Tony Lindgren
2012-11-20 17:57 ` Tony Lindgren
2012-11-20 23:00 ` Jon Hunter [this message]
2012-11-20 23:00 ` Jon Hunter
2012-11-28 15:18 ` Russell King - ARM Linux
2012-11-28 15:18 ` Russell King - ARM Linux
2012-11-28 21:43 ` Jon Hunter
2012-11-28 21:43 ` Jon Hunter
2012-11-28 14:04 ` Eduardo Valentin
2012-11-28 14:04 ` Eduardo Valentin
2012-11-28 15:16 ` Russell King - ARM Linux
2012-11-28 15:16 ` Russell King - ARM Linux
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=50AC0B83.9070704@ti.com \
--to=jon-hunter@ti.com \
--cc=eduardo.valentin@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=radhesh.fadnis@ti.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.