Messages in this thread |  | | | Date | Tue, 26 Aug 2008 22:24:18 +0200 | | From | Helge Deller <> | | Subject | Re: __kernel_suseconds_t is int on PA-RISC (and SPARC64)? |
| |
Geert Uytterhoeven wrote: > Apparently __kernel_suseconds_t is `int' on PA-RISC (and on SPARC64), > while it's `long' on all other platforms. > > Is there a specific reason for that?
I don't know for sure, but arch/parisc/kernel/syscall_table.S states: /* even though manpage says struct timeval contains longs, ours has * time_t and suseconds_t -- both of which are safe wide/narrow */ ENTRY_COMP(setitimer) So it was probably chosen to be int so that it can be easily used in 32- and 64bit kernels (or compat code).
Helge
> This causes compiler warnings in the HP SDC Real Time Clock driver, > which is shared between PA-RISC and m68k: > > drivers/input/misc/hp_sdc_rtc.c:461: warning: format '%02d' expects type 'int', but argument 4 has type 'long int' > drivers/input/misc/hp_sdc_rtc.c:461: warning: format '%02d' expects type 'int', but argument 4 has type 'long int' > drivers/input/misc/hp_sdc_rtc.c:468: warning: format '%02d' expects type 'int', but argument 4 has type 'long int' > drivers/input/misc/hp_sdc_rtc.c:468: warning: format '%02d' expects type 'int', but argument 4 has type 'long int' > drivers/input/misc/hp_sdc_rtc.c:475: warning: format '%02d' expects type 'int', but argument 4 has type 'long int' > drivers/input/misc/hp_sdc_rtc.c:475: warning: format '%02d' expects type 'int', but argument 4 has type 'long int' > drivers/input/misc/hp_sdc_rtc.c:482: warning: format '%02d' expects type 'int', but argument 4 has type 'long int' > drivers/input/misc/hp_sdc_rtc.c:482: warning: format '%02d' expects type 'int', but argument 4 has type 'long int' > drivers/input/misc/hp_sdc_rtc.c:489: warning: format '%02d' expects type 'int', but argument 4 has type 'long int' > drivers/input/misc/hp_sdc_rtc.c:489: warning: format '%02d' expects type 'int', but argument 4 has type 'long int' > > Gr{oetje,eeting}s, > > Geert
|  |