[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7145.1262711336@redhat.com>
Date: Tue, 05 Jan 2010 17:08:56 +0000
From: David Howells <dhowells@...hat.com>
To: john stultz <johnstul@...ibm.com>
Cc: dhowells@...hat.com, lkml <linux-kernel@...r.kernel.org>,
Koichi Yasutake <yasutake.koichi@...panasonic.com>,
linux-am33-list@...hat.com
Subject: Re: [RFC][PATCH 11/14] Convert mn10300 to read/update_persistent_clock
john stultz <johnstul@...ibm.com> wrote:
> This patch converts the mn10300 architecture to use the generic
> read_persistent_clock and update_persistent_clock interfaces, reducing
> the amount of arch specific code we have to maintain, and allowing for
> further cleanups in the future.
>
> I have not built or tested this patch, so help from arch maintainers
> would be appreciated.
>
> Signed-off-by: John Stultz <johnstul@...ibm.com>
arch/mn10300/kernel/rtc.c: In function `update_persistent_clock':
arch/mn10300/kernel/rtc.c:113: error: implicit declaration of function 'set_rtc_mms'
arch/mn10300/kernel/rtc.c: At top level:
arch/mn10300/kernel/rtc.c:24: warning: unused variable `last_rtc_update'
arch/mn10300/kernel/rtc.c:24: warning: 'last_rtc_update' defined but not used
arch/mn10300/kernel/rtc.c:51: warning: 'set_rtc_mmss' defined but not used
set_rtc_mms should be set_rtc_mmss in update_persistent_clock(). In fact,
set_rtc_mmss() should probably just be rolled into update_persistent_clock().
Furthermore, last_rtc_update and its comment should be deleted.
Apart from that, it seems to work.
David
--
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