Re: [PATCH] RTC: Fix infinite loop in initializing the alarm.

2014-04-08 Thread Alessandro Zummo
On Tue, 8 Apr 2014 00:54:42 +0200 Ales Novak wrote: > In __rtc_read_alarm(), if the alarm time retrieved by > rtc_read_alarm_internal() from the device contains invalid values > (e.g. month=2,mday=31) and the year not set (=-1), the initialization > will loop infinitely because the year-fixing

Re: [PATCH] RTC: Fix infinite loop in initializing the alarm.

2014-04-08 Thread Alessandro Zummo
On Tue, 8 Apr 2014 00:54:42 +0200 Ales Novak alno...@suse.cz wrote: In __rtc_read_alarm(), if the alarm time retrieved by rtc_read_alarm_internal() from the device contains invalid values (e.g. month=2,mday=31) and the year not set (=-1), the initialization will loop infinitely because the

[PATCH] RTC: Fix infinite loop in initializing the alarm.

2014-04-07 Thread Ales Novak
In __rtc_read_alarm(), if the alarm time retrieved by rtc_read_alarm_internal() from the device contains invalid values (e.g. month=2,mday=31) and the year not set (=-1), the initialization will loop infinitely because the year-fixing loop expects the time being invalid due to leap year. Fix

[PATCH] RTC: Fix infinite loop in initializing the alarm.

2014-04-07 Thread Ales Novak
In __rtc_read_alarm(), if the alarm time retrieved by rtc_read_alarm_internal() from the device contains invalid values (e.g. month=2,mday=31) and the year not set (=-1), the initialization will loop infinitely because the year-fixing loop expects the time being invalid due to leap year. Fix