[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <tip-0ceb4c3e3f1ccaf121851e33c3ea269b8ad0f219@git.kernel.org>
Date: Tue, 25 Aug 2009 07:13:27 GMT
From: tip-bot for Paul Mundt <lethal@...ux-sh.org>
To: linux-tip-commits@...r.kernel.org
Cc: linux-kernel@...r.kernel.org, hpa@...or.com, mingo@...hat.com,
schwidefsky@...ibm.com, lethal@...ux-sh.org, tglx@...utronix.de,
mingo@...e.hu
Subject: [tip:timers/core] timekeeping: Fix up read_persistent_clock() breakage on sh
Commit-ID: 0ceb4c3e3f1ccaf121851e33c3ea269b8ad0f219
Gitweb: http://git.kernel.org/tip/0ceb4c3e3f1ccaf121851e33c3ea269b8ad0f219
Author: Paul Mundt <lethal@...ux-sh.org>
AuthorDate: Tue, 25 Aug 2009 07:32:39 +0900
Committer: Ingo Molnar <mingo@...e.hu>
CommitDate: Tue, 25 Aug 2009 08:46:16 +0200
timekeeping: Fix up read_persistent_clock() breakage on sh
The recent commit "timekeeping: Increase granularity of
read_persistent_clock()" introduced read_persistent_clock()
rework which inadvertently broke the sh conversion:
arch/sh/kernel/time.c:45: error: passing argument 1 of 'rtc_sh_get_time' from incompatible pointer type
distcc[13470] ERROR: compile arch/sh/kernel/time.c on sprygo/32 failed
make[2]: *** [arch/sh/kernel/time.o] Error 1
This trivial fix gets it working again.
Signed-off-by: Paul Mundt <lethal@...ux-sh.org>
Cc: Martin Schwidefsky <schwidefsky@...ibm.com>
LKML-Reference: <20090824223239.GB20832@...ux-sh.org>
Signed-off-by: Ingo Molnar <mingo@...e.hu>
---
arch/sh/kernel/time.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/sh/kernel/time.c b/arch/sh/kernel/time.c
index 3f4706a..0e0e858 100644
--- a/arch/sh/kernel/time.c
+++ b/arch/sh/kernel/time.c
@@ -41,7 +41,7 @@ int (*rtc_sh_set_time)(const time_t) = null_rtc_set_time;
#ifdef CONFIG_GENERIC_CMOS_UPDATE
void read_persistent_clock(struct timespec *ts)
{
- rtc_sh_get_time(&ts);
+ rtc_sh_get_time(ts);
}
int update_persistent_clock(struct timespec now)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists