From: John Stultz <john.stultz@linaro.org>
To: lkml <linux-kernel@vger.kernel.org>
Cc: John Stultz <john.stultz@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>,
Miroslav Lichvar <mlichvar@redhat.com>,
Richard Cochran <richardcochran@gmail.com>,
Prarit Bhargava <prarit@redhat.com>,
Stephen Boyd <stephen.boyd@linaro.org>,
Shuah Khan <shuah@kernel.org>
Subject: [GIT PULL][PATCH 0/4] Timekeeping items for 4.13
Date: Tue, 20 Jun 2017 22:21:29 -0700 [thread overview]
Message-ID: <1498022493-20292-1-git-send-email-john.stultz@linaro.org> (raw)
Just a small set of changes, the biggest changes being the
MONOTONIC_RAW handling cleanup, and a new kselftest from
Miroslav. Also a a clear warning deprecating
CONFIG_GENERIC_TIME_VSYSCALL_OLD, which affects ppc and ia64.
Let me know if you have any thoughts or objections!
thanks
-john
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@kernel.org>
Cc: Miroslav Lichvar <mlichvar@redhat.com>
Cc: Richard Cochran <richardcochran@gmail.com>
Cc: Prarit Bhargava <prarit@redhat.com>
Cc: Stephen Boyd <stephen.boyd@linaro.org>
Cc: Shuah Khan <shuah@kernel.org>
The following changes since commit 8e6cec1c7c5afa489687c90be15d6ed82c742975:
Merge branch 'clockevents/4.12-fixes' of https://git.linaro.org/people/daniel.lezcano/linux into timers/urgent (2017-06-20 12:50:32 +0200)
are available in the git repository at:
https://git.linaro.org/people/john.stultz/linux.git fortglx/4.13/time
for you to fetch changes up to 767392565a3e618950fe1a5ff1ba11295f6332f4:
kselftests: timers: Add test for frequency step (2017-06-20 22:14:45 -0700)
----------------------------------------------------------------
John Stultz (2):
time: Clean up CLOCK_MONOTONIC_RAW time handling
time: Add warning about imminent deprecation of
CONFIG_GENERIC_TIME_VSYSCALL_OLD
Miroslav Lichvar (2):
kselftests: timers: Fix inconsistency-check to not ignore first
timestamp
kselftests: timers: Add test for frequency step
arch/arm64/kernel/vdso.c | 6 +-
include/linux/timekeeper_internal.h | 4 +-
kernel/time/timekeeping.c | 46 ++--
tools/testing/selftests/timers/Makefile | 5 +-
tools/testing/selftests/timers/freq-step.c | 268 +++++++++++++++++++++
.../testing/selftests/timers/inconsistency-check.c | 4 +-
6 files changed, 303 insertions(+), 30 deletions(-)
create mode 100644 tools/testing/selftests/timers/freq-step.c
--
2.7.4
next reply other threads:[~2017-06-21 5:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-21 5:21 John Stultz [this message]
2017-06-21 5:21 ` [PATCH 1/4] time: Clean up CLOCK_MONOTONIC_RAW time handling John Stultz
2017-06-21 9:36 ` Will Deacon
2017-06-21 5:21 ` [PATCH 2/4] time: Add warning about imminent deprecation of CONFIG_GENERIC_TIME_VSYSCALL_OLD John Stultz
2017-06-21 6:11 ` Paul Mackerras
2017-06-21 6:23 ` John Stultz
2017-06-21 6:15 ` Michael Ellerman
2017-06-21 5:21 ` [PATCH 3/4] kselftests: timers: Fix inconsistency-check to not ignore first timestamp John Stultz
2017-06-21 5:21 ` [PATCH 4/4] kselftests: timers: Add test for frequency step John Stultz
2017-06-21 5:23 ` [GIT PULL][PATCH 0/4] Timekeeping items for 4.13 John Stultz
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=1498022493-20292-1-git-send-email-john.stultz@linaro.org \
--to=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mlichvar@redhat.com \
--cc=prarit@redhat.com \
--cc=richardcochran@gmail.com \
--cc=shuah@kernel.org \
--cc=stephen.boyd@linaro.org \
--cc=tglx@linutronix.de \
/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