if (ntp_synced() && 
if (ppc_md.set_rtc_time && ntp_synced() && 
static __inline__ void timer_check_rtc(void){        /*         * update the rtc when needed, this should be performed on the         * right fraction of a second. Half or full second ?         * Full second works on mk48t59 clocks, others need testing.         * Note that this update is basically only used through          * the adjtimex system calls. Setting the HW clock in         * any other way is a /dev/rtc and userland business.         * This is still wrong by -0.5/+1.5 jiffies because of the         * timer interrupt resolution and possible delay, but here we          * hit a quantization limit which can only be solved by higher         * resolution timers and decoupling time management from timer         * interrupts. This is also wrong on the clocks         * which require being written at the half second boundary.         * We should have an rtc call that only sets the minutes and         * seconds like on Intel to avoid problems with non UTC clocks.         */        if (ntp_synced() &&	    xtime.tv_sec - last_rtc_update >= 659 &&	    abs((xtime.tv_nsec/1000) - (1000000-1000000/HZ)) < 500000/HZ &&	    jiffies - wall_jiffies == 1) {		struct rtc_time tm;		to_tm(xtime.tv_sec + 1 + timezone_offset, &tm);		tm.tm_year -= 1900;		tm.tm_mon -= 1;		if (ppc_md.set_rtc_time(&tm) == 0)			last_rtc_update = xtime.tv_sec + 1;		else			/* Try again one minute later */			last_rtc_update += 60;        }}
4520	/local/tlutelli/issta_data/temp/c/2005_temp/2005/4520/d2e615125762459fd2bb9f0c91881509a0b9c31b/time.c/clean/arch/powerpc/kernel/time.c