Re: [pm:linux-next 9/38] kernel/time/timekeeping.c:736:2: error: implicit declaration of function 'clockevents_resume'

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

On Thursday, August 09, 2012, Fengguang Wu wrote:
> Hi Rafael,
> 
> FYI, kernel build failed on
> 
> tree:   git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git linux-next
> head:   9ea3f7070730c4148694904a335825f7e4540604
> commit: a2c2042496a64a555ae383a90bc0ab17f37e92f4 [9/38] timekeeping: Add suspend and resume of clock event devices
> config: cris-etrax-100lx_v2_defconfig (attached as .config)
> 
> All related error/warning messages:
> 
> kernel/time/timekeeping.c: In function 'timekeeping_resume':
> kernel/time/timekeeping.c:736:2: error: implicit declaration of function 'clockevents_resume' [-Werror=implicit-function-declaration]
> kernel/time/timekeeping.c: In function 'timekeeping_suspend':
> kernel/time/timekeeping.c:795:2: error: implicit declaration of function 'clockevents_suspend' [-Werror=implicit-function-declaration]
> cc1: some warnings being treated as errors
> 
> vim +736 kernel/time/timekeeping.c
>    733	
>    734		read_persistent_clock(&ts);
>    735	
>  > 736		clockevents_resume();
>    737		clocksource_resume();
>    738	
>    739		write_seqlock_irqsave(&timekeeper.lock, flags);
> 

That most likely is due to CONFIG_GENERIC_CLOCKEVENTS_BUILD unset.  Should be
fixed now.

Thanks,
Rafael
--
To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Kernel Development]     [Kernel Announce]     [Kernel Newbies]     [Linux Networking Development]     [Share Photos]     [IDE]     [Security]     [Git]     [Netfilter]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Device Mapper]

  Powered by Linux