On Fri, Jan 07, 2011 at 08:24:26PM +0530, Santosh Shilimkar wrote: > > -----Original Message----- > > From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap- > > ow...@vger.kernel.org] On Behalf Of Russell King - ARM Linux > > Sent: Friday, January 07, 2011 8:11 PM > > To: linux-omap@vger.kernel.org > > Subject: Re: Latest regressions > > > > While trying to build the latest kernel for the SDP4430 board: > > > > arch/arm/mach-omap2/clockdomain.c: In function │_enable_hwsup│: > > arch/arm/mach-omap2/clockdomain.c:251: error: │struct clockdomain│ > > has no member named │clktrctrl_mask│ > > arch/arm/mach-omap2/clockdomain.c:254: error: │struct clockdomain│ > > has no member named │clktrctrl_mask│ > > arch/arm/mach-omap2/clockdomain.c: In function │_disable_hwsup│: > > arch/arm/mach-omap2/clockdomain.c:277: error: │struct clockdomain│ > > has no member named │clktrctrl_mask│ > > arch/arm/mach-omap2/clockdomain.c:280: error: │struct clockdomain│ > > has no member named │clktrctrl_mask│ > > arch/arm/mach-omap2/clockdomain.c: In function │omap2_clkdm_sleep│: > > arch/arm/mach-omap2/clockdomain.c:744: error: │struct clockdomain│ > > has no member named │clktrctrl_mask│ > > arch/arm/mach-omap2/clockdomain.c: In function │omap2_clkdm_wakeup│: > > arch/arm/mach-omap2/clockdomain.c:789: error: │struct clockdomain│ > > has no member named │clktrctrl_mask│ > > arch/arm/mach-omap2/clockdomain.c: In function > > │omap2_clkdm_clk_enable│: > > arch/arm/mach-omap2/clockdomain.c:922: error: │struct clockdomain│ > > has no member named │clktrctrl_mask│ > > arch/arm/mach-omap2/clockdomain.c:926: error: │struct clockdomain│ > > has no member named │clktrctrl_mask│ > > arch/arm/mach-omap2/clockdomain.c: In function > > │omap2_clkdm_clk_disable│: > > arch/arm/mach-omap2/clockdomain.c:994: error: │struct clockdomain│ > > has no member named │clktrctrl_mask│ > > arch/arm/mach-omap2/clockdomain.c:998: error: │struct clockdomain│ > > has no member named │clktrctrl_mask│ > > > > Linus' tree prior to the OMAP merge is buildable for the same > > config. > :) This one is also fixed with the series but would get merged in rc1 > http://www.mail-archive.com/linux-omap@vger.kernel.org/msg41712.html
It's something that should be queued up to also go in during the merge window IMHO. Let's try to make rc1 a little less problematical than it currently is. -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
