linux-kernel.vger.kernel.org archive mirror
 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>
Subject: [GIT PULL] Timekeeping changes for 3.12
Date: Thu, 22 Aug 2013 14:11:23 -0700	[thread overview]
Message-ID: <52167E7B.7060606@linaro.org> (raw)

Hey Thomas,
    Just wanted to send you my fortglx/3.12/time branch for tip/timers/core.

There's also the fortglx/3.12/sched-clock64-base branch, which I sent
you an earlier pull request, but haven't seen anything on.

Let me know if you have any objections or comments.

thanks
-john



The following changes since commit 07862c1cd6675cde2dd4bd64e64d704ea2185b79:

  ARM: clocksource: Add support for MOXA ART SoCs (2013-07-18 15:27:47
+0200)

are available in the git repository at:

  git://git.linaro.org/people/jstultz/linux.git fortglx/3.12/time

for you to fetch changes up to a97ad0c4b447a132a322cedc3a5f7fa4cab4b304:

  ntp: Make periodic RTC update more reliable (2013-08-22 12:33:38 -0700)

----------------------------------------------------------------
Miroslav Lichvar (1):
      ntp: Make periodic RTC update more reliable

Prarit Bhargava (1):
      clocksource: Fix !CONFIG_CLOCKSOURCE_WATCHDOG compile

Zoran Markovic (1):
      rtc: Keep system awake until all expired RTC timers are handled

 drivers/rtc/interface.c   | 13 +++++++++----
 kernel/time/clocksource.c |  1 +
 kernel/time/ntp.c         |  3 ++-
 3 files changed, 12 insertions(+), 5 deletions(-)

             reply	other threads:[~2013-08-22 21:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-22 21:11 John Stultz [this message]
2013-08-29 21:56 ` [GIT PULL] Timekeeping changes 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=52167E7B.7060606@linaro.org \
    --to=john.stultz@linaro.org \
    --cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).