On Tue, Nov 20, 2012 at 05:00:19PM -0600, Jon Hunter wrote: > > On 11/20/2012 11:57 AM, Tony Lindgren wrote: > > * Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx> [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 Well, it's now two weeks on, and the warning is still there... what's going on? Why aren't fixes propagating upstream? -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
