From: john.stultz@linaro.org (John Stultz)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] 64bit friendly generic sched_clock() base for 3.12
Date: Tue, 30 Jul 2013 11:50:49 -0700 [thread overview]
Message-ID: <51F80B09.8060509@linaro.org> (raw)
Hey Thomas, Olof,
Here is the common base changes in Stephen's "64bit friendly
generic sched_clock()" patch series. This common base will be needed so
that following patch series can be merged via both the tip/timers/core
and arm-soc trees independently.
Please let me know if you have any issues or objections with this set.
thanks
-john
The following changes since commit ad81f0545ef01ea651886dddac4bef6cec930092:
Linux 3.11-rc1 (2013-07-14 15:18:27 -0700)
are available in the git repository at:
git://git.linaro.org/people/jstultz/linux.git
fortglx/3.12/sched-clock64-base
for you to fetch changes up to e7e3ff1bfe9c42ee31172e9afdc0383a9e595e29:
sched_clock: Add support for >32 bit sched_clock (2013-07-30 11:24:21
-0700)
----------------------------------------------------------------
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
include/linux/clocksource.h | 2 +
include/linux/sched_clock.h | 2 +
kernel/time/clocksource.c | 45 ++++++++++++------
kernel/time/sched_clock.c | 111
++++++++++++++++++++++++--------------------
4 files changed, 95 insertions(+), 65 deletions(-)
next reply other threads:[~2013-07-30 18:50 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-30 18:50 John Stultz [this message]
2013-07-31 22:30 ` [PATCH 00/18] Convert arm sched_clock users to sched_clock_register() Stephen Boyd
2013-07-31 22:31 ` [PATCH 01/18] ARM: timer-sp: Switch " Stephen Boyd
2013-07-31 22:31 ` [PATCH 02/18] ARM: clps711x: " Stephen Boyd
2013-07-31 22:31 ` [PATCH 03/18] ARM: davinci: " Stephen Boyd
2013-08-01 5:46 ` Sekhar Nori
2013-07-31 22:31 ` [PATCH 04/18] ARM: imx: " Stephen Boyd
2013-07-31 22:31 ` [PATCH 05/18] ARM: integrator: " Stephen Boyd
2013-08-07 13:52 ` Linus Walleij
2013-07-31 22:31 ` [PATCH 06/18] ARM: IXP4xx: " Stephen Boyd
2013-08-09 7:49 ` Krzysztof Halasa
2013-07-31 22:31 ` [PATCH 07/18] ARM: mmp: " Stephen Boyd
2013-07-31 22:31 ` [PATCH 08/18] ARM: msm: " Stephen Boyd
2013-08-01 16:12 ` David Brown
2013-07-31 22:31 ` [PATCH 09/18] ARM: OMAP1: " Stephen Boyd
2013-07-31 22:31 ` [PATCH 10/18] ARM: OMAP2+: " Stephen Boyd
2013-08-01 0:43 ` Santosh Shilimkar
2013-07-31 22:31 ` [PATCH 11/18] ARM: pxa: " Stephen Boyd
2013-07-31 22:31 ` [PATCH 12/18] ARM: sa1100: " Stephen Boyd
2013-07-31 22:31 ` [PATCH 13/18] ARM: u300: " Stephen Boyd
2013-08-07 18:55 ` Linus Walleij
2013-07-31 22:31 ` [PATCH 14/18] ARM: iop: " Stephen Boyd
2013-07-31 22:31 ` [PATCH 15/18] ARM: OMAP: " Stephen Boyd
2013-07-31 22:31 ` [PATCH 16/18] ARM: orion: " Stephen Boyd
2013-08-01 0:31 ` Jason Cooper
2013-07-31 22:31 ` [PATCH 17/18] ARM: SAMSUNG: " Stephen Boyd
2013-08-05 17:22 ` Kukjin Kim
2013-07-31 22:31 ` [PATCH 18/18] ARM: versatile: " Stephen Boyd
2013-08-29 21:56 ` [GIT PULL] 64bit friendly generic sched_clock() base for 3.12 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=51F80B09.8060509@linaro.org \
--to=john.stultz@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).