RTC: Properly handle rtc_read_alarm error propagation and fix bug
authorJohn Stultz <john.stultz@linaro.org>
Thu, 20 Jan 2011 23:26:13 +0000 (15:26 -0800)
committerThomas Gleixner <tglx@linutronix.de>
Fri, 21 Jan 2011 16:38:19 +0000 (17:38 +0100)
commitd5553a556165535337ece8592f066407c62eec2e
tree2b9eaf6a5b9a4939f92cadedf6c797070107e7af
parentaa0be0f4659f91f31e45adc422b1788cb36ffddc
RTC: Properly handle rtc_read_alarm error propagation and fix bug

In reviewing cases where the virtualized interfaces didn't propagate
errors properly, I noticed rtc_read_alarm needed fixing. In doing
so I noticed my RTC rework dropped a memset and that the behavior
of rtc_read_alarm shouldn't be conditionalized on the alarm.enabled
flag (as the alarm may be set, but the irqs may be disabled). So
those were corrected as well.

CC: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: John Stultz <john.stultz@linaro.org>
LKML-Reference: <1295565973-14358-2-git-send-email-john.stultz@linaro.org>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
drivers/rtc/interface.c