On Sun, 19 Apr 2009 20:41:21 +0200
Geert Uytterhoeven <geert@xxxxxxxxxxxxxx> wrote:
please implement either set_time or set_mmss, not both.
I don't know the chip but I suspect set_time is the one you need.
OK, I will remove .set_mmss. Got to confused by looking into how
everything is used...
BTW, the only remaining users of rtc_set_mmss() seem to be
arch/sparc/kernel/time_{32,64}.c?
Yes. The facility is there for drives, not users. For some chips it's easier
to implement a set_mmss like interface so it's better to have the rtc framewrk
to convert between the twos than to have repeated code in drivers.
OK, if I take the result (for both rtc-rp5c01 and rtc-msm6242) through
the m68k tree?
that's ok, you can add my acked by.
--
Best regards,
Alessandro Zummo,
Tower Technologies - Torino, Italy
http://www.towertech.it
--
To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html