From: Al Viro <viro@ZenIV.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: [git pull] vfs.git part 4
Date: Wed, 5 Jul 2017 08:14:56 +0100 [thread overview]
Message-ID: <20170705071456.GB10672@ZenIV.linux.org.uk> (raw)
Continuation of timers-related stuff (there had been more, but
my parts of that series are already merged via timers/core). This
is more of y2038 work by Deepa Dinamani, partially disrupted by
the unification of native and compat timers-related syscalls.
The following changes since commit 938e7cf2d569833a5acf689a8926faf507826253:
posix-timers: Make nanosleep timespec argument const (2017-06-14 00:00:47 +0200)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git timers-compat
for you to fetch changes up to 725816e8aabb1c183baa2bc9572ab9a0d26b9ea1:
posix_clocks: Use get_itimerspec64() and put_itimerspec64() (2017-06-30 04:15:02 -0400)
----------------------------------------------------------------
Deepa Dinamani (7):
time: add get_timespec64 and put_timespec64
time: introduce {get,put}_itimerspec64
posix-stubs: Conditionally include COMPAT_SYS_NI defines
posix-timers: Use get_timespec64() and put_timespec64()
nanosleep: Use get_timespec64() and put_timespec64()
timerfd: Use get_itimerspec64() and put_itimerspec64()
posix_clocks: Use get_itimerspec64() and put_itimerspec64()
fs/timerfd.c | 43 +++++++-------
include/linux/compat.h | 6 ++
include/linux/hrtimer.h | 2 +-
include/linux/posix-timers.h | 1 -
include/linux/time.h | 18 ++++++
kernel/compat.c | 65 +++++++++++++++++++++
kernel/time/alarmtimer.c | 4 +-
kernel/time/hrtimer.c | 30 +++++-----
kernel/time/posix-cpu-timers.c | 8 +--
kernel/time/posix-stubs.c | 96 +++++++++++++++++--------------
kernel/time/posix-timers.c | 127 ++++++++++++++++-------------------------
kernel/time/time.c | 58 +++++++++++++++++++
12 files changed, 287 insertions(+), 171 deletions(-)
reply other threads:[~2017-07-05 7:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170705071456.GB10672@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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 NNTP newsgroup(s).