mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: John Stultz <john.stultz@linaro.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: lkml <linux-kernel@vger.kernel.org>,
	Richard Cochran <richardcochran@gmail.com>
Subject: [GIT PULL] Timekeeping changes for 3.6
Date: Wed, 20 Jun 2012 17:57:44 -0700	[thread overview]
Message-ID: <4FE27188.3040402@linaro.org> (raw)

Hey Thomas,

     Just wanted to send a pull request for my current timekeeping queue 
for 3.6.

Let me know if you have any concerns or objections.

thanks
-john

You can find it here against current tip/timers/core:
   git://git.linaro.org/people/jstultz/linux.git fortglx/3.6/time

for you to fetch changes up to 406d3845a5b75129277576034a0b260c90495dc9:

   time: Kill xtime_lock, replacing it with jiffies_lock (2012-06-20 
20:26:58 -0400)

----------------------------------------------------------------
John Stultz (8):
       time: Condense timekeeper.xtime into xtime_sec
       time: Rework timekeeping functions to take timekeeper ptr as argument
       time: Refactor accumulation of nsecs to secs
       time: Whitespace cleanups per Ingo's requests
       time: Explicitly use u32 instead of int for shift values
       time: Move TAI managment into timekeeping core from ntp
       time: Add CLOCK_TAI clockid
       time: Kill xtime_lock, replacing it with jiffies_lock

  drivers/clocksource/i8253.c |    2 +-
  include/linux/jiffies.h     |    3 +-
  include/linux/time.h        |    9 +-
  kernel/posix-timers.c       |   10 +
  kernel/time/jiffies.c       |    6 +-
  kernel/time/ntp.c           |   18 +-
  kernel/time/tick-common.c   |    8 +-
  kernel/time/tick-internal.h |    1 -
  kernel/time/tick-sched.c    |   22 +--
  kernel/time/timekeeping.c   |  461 
++++++++++++++++++++++++++-----------------
  10 files changed, 332 insertions(+), 208 deletions(-)


                 reply	other threads:[~2012-06-21  0:57 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=4FE27188.3040402@linaro.org \
    --to=john.stultz@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=richardcochran@gmail.com \
    --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

Powered by JetHome