| To: | Brad Parker <brad@parker.boston.ma.us> |
|---|---|
| Subject: | Re: to_tm() in kernel/time.c? |
| From: | Jun Sun <jsun@mvista.com> |
| Date: | Tue, 9 Dec 2003 14:19:40 -0800 |
| Cc: | linux-mips@linux-mips.org, jsun@mvista.com |
| In-reply-to: | <200312092058.hB9Kw6t31608@p2.parker.boston.ma.us>; from brad@parker.boston.ma.us on Tue, Dec 09, 2003 at 03:58:06PM -0500 |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <200312092058.hB9Kw6t31608@p2.parker.boston.ma.us> |
| Sender: | linux-mips-bounce@linux-mips.org |
| User-agent: | Mutt/1.2.5i |
On Tue, Dec 09, 2003 at 03:58:06PM -0500, Brad Parker wrote:
>
> Can anyone tell me if to_tm() in kernel/time.c returns months as 0-11?
> (in the current mips tree, that is)
>
It is 0-11. See the code
tm->tm_mon = i - 1; /* tm_mon starts from 0 to 11 */
> I'm curious if the to_tm() in the ppc tree is the same as the to_tm()
> in the mips tree. In the ppc tree it returns 1-12.
>
The routine was copied from PPC. I think tm_mon is set to 0-11 so as to match
struct rtc_time usage when it is exported to userland.
I will check with PPC folks to see why they changed it.
Jun
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Kernel 2.4.23 on Cobalt Qube2, Kumba |
|---|---|
| Next by Date: | Re: Kernel 2.4.23 on Cobalt Qube2, Kumba |
| Previous by Thread: | to_tm() in kernel/time.c?, Brad Parker |
| Next by Thread: | [PATCH] au1k_ir - fix for 2.6, Stephen Hemminger |
| Indexes: | [Date] [Thread] [Top] [All Lists] |