From: John Stultz <john.stultz@linaro.org>
To: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] First set of timekeeping changes for 3.13
Date: Tue, 17 Sep 2013 11:13:49 -0700 [thread overview]
Message-ID: <52389BDD.8070801@linaro.org> (raw)
Hey Thomas, Ingo,
So these were items I had hoped to get merged in 3.12, but I'm
guessing got buried in Thomas inbox while he was traveling/busy (and its
my fault for not cc'ing Ingo). So now 3.12-rc1 is out, I wanted to send
this in for tip/timers/core right away so these don't get missed in this
next cycle.
Please let me know if there are any objections or issues with these changes.
thanks
-john
The following changes since commit 272b98c6455f00884f0350f775c5342358ebb73f:
Linux 3.12-rc1 (2013-09-16 16:17:51 -0400)
are available in the git repository at:
git://git.linaro.org/people/jstultz/linux.git fortglx/3.13/time
for you to fetch changes up to 389e067032fbb96e439abafae848dd447e4cafb4:
Merge branch 'fortglx/3.12/time' into fortglx/3.13/time (2013-09-16
18:54:07 -0700)
----------------------------------------------------------------
John Stultz (2):
Merge branch 'fortglx/3.12/sched-clock64-base' into fortglx/3.13/time
Merge branch 'fortglx/3.12/time' into fortglx/3.13/time
Miroslav Lichvar (1):
ntp: Make periodic RTC update more reliable
Prarit Bhargava (1):
clocksource: Fix !CONFIG_CLOCKSOURCE_WATCHDOG compile
Stephen Boyd (4):
clocksource: Extract max nsec calculation into separate function
sched_clock: Use seqcount instead of rolling our own
sched_clock: Use an hrtimer instead of timer
sched_clock: Add support for >32 bit sched_clock
Zoran Markovic (1):
rtc: Keep system awake until all expired RTC timers are handled
drivers/rtc/interface.c | 13 ++++--
include/linux/clocksource.h | 2 +
include/linux/sched_clock.h | 2 +
kernel/time/clocksource.c | 46 ++++++++++++------
kernel/time/ntp.c | 3 +-
kernel/time/sched_clock.c | 111
++++++++++++++++++++++++--------------------
6 files changed, 107 insertions(+), 70 deletions(-)
reply other threads:[~2013-09-17 18:13 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=52389BDD.8070801@linaro.org \
--to=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.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