linux-kernel - [GIT PULL] Timekeeping changes for 3.12

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <52167E7B.7060606@linaro.org>
Date:	Thu, 22 Aug 2013 14:11:23 -0700
From:	John Stultz <john.stultz@...aro.org>
To:	Thomas Gleixner <tglx@...utronix.de>
CC:	LKML <linux-kernel@...r.kernel.org>
Subject: [GIT PULL] Timekeeping changes for 3.12

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(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/