Displaying 5 results from an estimated 5 matches for "__kernel_time_t".
2015 May 18
5
kernel/libc uapi changes for y2038
...that can be set to either 32 or 64 for 32-bit architectures by
the libc. Depending on that macro, the compiler will either see one
of these combinations (for each of the five structures):
a) __BITS_PER_LONG == 32 && __KERNEL_TIME_BITS == 32:
struct timespec based on 32-bit __kernel_time_t
struct __kernel_timespec based on 64-bit __kernel_time64_t
b) __BITS_PER_LONG == 64 && __KERNEL_TIME_BITS == 64:
struct timespec based on 64-bit __kernel_time_t
struct __kernel_timespec based on 64-bit __kernel_time64_t
c) __BITS_PER_LONG == 32 && __...
2015 May 27
0
kernel/libc uapi changes for y2038
...r 64 for 32-bit architectures by
> the libc. Depending on that macro, the compiler will either see one
> of these combinations (for each of the five structures):
>
> a) __BITS_PER_LONG == 32 && __KERNEL_TIME_BITS == 32:
>
> struct timespec based on 32-bit __kernel_time_t
> struct __kernel_timespec based on 64-bit __kernel_time64_t
>
> b) __BITS_PER_LONG == 64 && __KERNEL_TIME_BITS == 64:
>
> struct timespec based on 64-bit __kernel_time_t
> struct __kernel_timespec based on 64-bit __kernel_time64_t
>
>...
2002 May 07
0
Re: SAMBA compile errors at XFS kernel.. (fwd)
...>
> thanks.
>
>
> On Wed, May 08, 2002 at 12:40:55AM +0200, Jan Kara wrote:
> > Hello,
> >
> > Umm.. I can understand complaints of compiler about __kernel_uid32_t
> > in the definition of qid_t. But I can't understand those problem with
> > __kernel_time_t. I can't see it anywhere in the quota.h - even time_t
> > is in #ifdef __KERNEL__. Anyway creating userspace version of header
> > is probably the right way out of problems... I'll try to create some
> > userspace header file...
> >
> > Honza
> >
> &...
2023 Jan 14
1
[klibc:time64] time: Use 64-bit time types on all architectures
...BIG_ENDIAN && __BITS_PER_LONG == 32
+ long __tv_pad;
+#endif
+ long tv_nsec;
+#if __BYTE_ORDER == __LITTLE_ENDIAN && __BITS_PER_LONG == 32
+ long __tv_pad;
+#endif
+};
+
+struct timeval {
+ __kernel_time64_t tv_sec;
+ __kernel_suseconds_t tv_usec;
+};
+
+struct timeval_old {
+ __kernel_time_t tv_sec;
+ __kernel_suseconds_t tv_usec;
+};
+
+struct itimerspec {
+ struct timespec it_interval;
+ struct timespec it_value;
+};
+
+struct itimerval {
+ struct timeval_old it_interval;
+ struct timeval_old it_value;
+};
+
+struct timezone {
+ int tz_minuteswest;
+ int tz_dsttime;
+};
+
+#define I...
2012 May 15
5
[PATCH 0/5] resubmitting pending patches
Hi,
I?ve gone through the mailing list archives and hereby want
to resubmit my pending patches. Most are independent of each
other, except the m68k patch which will only be complete if
sigsuspend is also fixed. (It can be applied before that,
though.)
http://www.zytor.com/pipermail/klibc/2012-January/003173.html
[PATCH] fix m68k support
Resubmitted here as 0005. While there was a question from