From: Lukasz Majewski <lukma@denx.de>
To: Joseph Myers <joseph@codesourcery.com>, Paul Eggert <eggert@cs.ucla.edu>
Cc: Alistair Francis <alistair23@gmail.com>,
Alistair Francis <alistair.francis@wdc.com>,
GNU C Library <libc-alpha@sourceware.org>,
Adhemerval Zanella <adhemerval.zanella@linaro.org>,
Florian Weimer <fweimer@redhat.com>,
Florian Weimer <fw@deneb.enyo.de>,
Zack Weinberg <zackw@panix.com>,
Carlos O'Donell <carlos@redhat.com>,
Lukasz Majewski <lukma@denx.de>
Subject: [PATCH 0/5] y2038: linux: timer_[sg]ettime conversion to 64 bit time
Date: Mon, 11 Nov 2019 22:47:53 +0100 [thread overview]
Message-ID: <20191111214758.3677-1-lukma@denx.de> (raw)
This patch series converts timer_[sg]ettime functions to support
64 bit time.
The glibc internal struct __itimerspec64 is introduced in first patch.
Two next patches decouple x86_64 specific timer_[sg]ettime implementations
from the Linux generic ones for easier conversion (as x86_64 already
supports 64 bit time).
Two last patches are converting Linux generic timer syscalls.
Lukasz Majewski (5):
time: Introduce glibc's internal struct __itimerspec64
timer: Decouple x86_64 specific timer_gettime from generic Linux
implementation
timer: Decouple x86_64 specific timer_settime from generic Linux
implementation
y2038: linux: Provide __timer_gettime64 implementation
y2038: linux: Provide __timer_settime64 implementation
include/time.h | 27 +++++++
sysdeps/unix/sysv/linux/timer_gettime.c | 49 ++++++++++---
sysdeps/unix/sysv/linux/timer_settime.c | 71 ++++++++++++++++---
.../unix/sysv/linux/x86_64/timer_gettime.c | 12 ++--
.../unix/sysv/linux/x86_64/timer_settime.c | 14 ++--
5 files changed, 144 insertions(+), 29 deletions(-)
--
2.20.1
next reply other threads:[~2019-11-11 21:48 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-11 21:47 Lukasz Majewski [this message]
2019-11-11 21:47 ` [PATCH 1/5] time: Introduce glibc's internal struct __itimerspec64 Lukasz Majewski
2019-11-27 16:59 ` Lukasz Majewski
2019-12-04 19:41 ` Adhemerval Zanella
2019-11-11 21:47 ` [PATCH 2/5] timer: Decouple x86_64 specific timer_gettime from generic Linux implementation Lukasz Majewski
2019-11-27 16:59 ` Lukasz Majewski
2019-12-04 19:41 ` Adhemerval Zanella
2019-11-11 21:47 ` [PATCH 3/5] timer: Decouple x86_64 specific timer_settime " Lukasz Majewski
2019-11-27 16:59 ` Lukasz Majewski
2019-12-04 19:41 ` Adhemerval Zanella
2019-11-11 21:47 ` [PATCH 4/5] y2038: linux: Provide __timer_gettime64 implementation Lukasz Majewski
2019-11-27 17:00 ` Lukasz Majewski
2019-12-04 19:41 ` Adhemerval Zanella
2019-12-05 9:42 ` Lukasz Majewski
2019-12-11 17:51 ` Andreas Schwab
2019-12-11 22:26 ` Lukasz Majewski
2019-12-12 15:26 ` Andreas Schwab
2019-12-12 15:33 ` Lukasz Majewski
2019-12-12 15:46 ` Andreas Schwab
2019-12-12 16:05 ` Lukasz Majewski
2019-12-12 16:08 ` Andreas Schwab
2019-11-11 21:47 ` [PATCH 5/5] y2038: linux: Provide __timer_settime64 implementation Lukasz Majewski
2019-11-27 17:00 ` Lukasz Majewski
2019-12-04 19:41 ` Adhemerval Zanella
2019-11-18 22:00 ` [PATCH 0/5] y2038: linux: timer_[sg]ettime conversion to 64 bit time Lukasz Majewski
2019-11-25 8:34 ` Lukasz Majewski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191111214758.3677-1-lukma@denx.de \
--to=lukma@denx.de \
--cc=adhemerval.zanella@linaro.org \
--cc=alistair.francis@wdc.com \
--cc=alistair23@gmail.com \
--cc=carlos@redhat.com \
--cc=eggert@cs.ucla.edu \
--cc=fw@deneb.enyo.de \
--cc=fweimer@redhat.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=zackw@panix.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).