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

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Mon, 10 Mar 2014 11:32:34 -0700
From:	John Stultz <john.stultz@...aro.org>
To:	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...nel.org>
CC:	LKML <linux-kernel@...r.kernel.org>,
	Greg Hackmann <ghackmann@...gle.com>,
	Rashika Kheria <rashika.kheria@...il.com>
Subject: [GIT PULL] Timekeeping changes for 3.15

Hey Thomas, Ingo,

 My queue is pretty short (and small) for 3.15, but I wanted to send it
along for tip/timers/core.

Let me know if you have any feedback or objections.

thanks
-john


The following changes since commit 03d11a0e458d7008192585124e4c3313c2829046:

  Merge tag 'for-v3.14' of git://git.infradead.org/battery-2.6
(2014-01-21 11:36:20 -0800)

are available in the git repository at:


  git://git.linaro.org/people/john.stultz/linux.git fortglx/3.15/time

for you to fetch changes up to 64e8d20bd39b81994d9cd60e7b42f8ec8652f5af:

  kernel: Include appropriate header file in time/timekeeping_debug.c
(2014-03-02 20:52:58 -0800)

----------------------------------------------------------------
Greg Hackmann (1):
      timerfd: support CLOCK_BOOTTIME clock

Rashika Kheria (1):
      kernel: Include appropriate header file in time/timekeeping_debug.c

 fs/timerfd.c                    | 1 +
 kernel/time/timekeeping_debug.c | 2 ++
 2 files changed, 3 insertions(+)

--
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/