From 9ce3c4d835740a708ff9acd8500b927053708d65 Mon Sep 17 00:00:00 2001 From: Feng Tang Date: Wed, 17 Nov 2010 12:11:24 +0000 Subject: [PATCH] --- yaml --- r: 224077 b: refs/heads/master c: d3e1884bc585a43674d2cb0d3f0aeeb0ae43bc04 h: refs/heads/master i: 224075: 17c32e8bd18b479f6e2e39b893d4eed67919f188 v: v3 --- [refs] | 2 +- trunk/drivers/rtc/rtc-mrst.c | 6 +++++- 2 files changed, 6 insertions(+), 2 deletions(-) diff --git a/[refs] b/[refs] index a0d9277fcc2e..366c47d3f30c 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: ad02519a0d27da4a0a50cbc696e810c94e27c28e +refs/heads/master: d3e1884bc585a43674d2cb0d3f0aeeb0ae43bc04 diff --git a/trunk/drivers/rtc/rtc-mrst.c b/trunk/drivers/rtc/rtc-mrst.c index 67b6be2b874d..bcd0cf63eb16 100644 --- a/trunk/drivers/rtc/rtc-mrst.c +++ b/trunk/drivers/rtc/rtc-mrst.c @@ -66,7 +66,11 @@ static inline int is_intr(u8 rtc_intr) * rtc_time's year contains the increment over 1900, but vRTC's YEAR * register can't be programmed to value larger than 0x64, so vRTC * driver chose to use 1960 (1970 is UNIX time start point) as the base, - * and does the translation at read/write time + * and does the translation at read/write time. + * + * Why not just use 1970 as the offset? it's because using 1960 will + * make it consistent in leap year setting for both vrtc and low-level + * physical rtc devices. */ static int mrst_read_time(struct device *dev, struct rtc_time *time) {