linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: john stultz <johnstul@us.ibm.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@elte.hu>, lkml <linux-kernel@vger.kernel.org>,
	Hector Palacios <hector.palacios@digi.com>
Subject: [GIT PULL] ktime_get fix for arch_gettimeoffset users
Date: Thu, 17 Nov 2011 14:59:31 -0800	[thread overview]
Message-ID: <1321570771.25715.49.camel@work-vm> (raw)

Hey Thomas,
	Here's a fix from Hector Palacios for ktime_get/ktime_get_ts on systems
that utilize arch_gettimeoffset() that should probably go in for 3.2

thanks
-john

The fix against current tip/timers/core can be found here:
  git://git.linaro.org/people/jstultz/linux.git fortglx/3.2/tip/timers/core

Hector Palacios (1):
      timekeeping: add arch_offset hook to ktime_get functions

 kernel/time/timekeeping.c |    4 ++++
 1 files changed, 4 insertions(+), 0 deletions(-)


                 reply	other threads:[~2011-11-17 23:00 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=1321570771.25715.49.camel@work-vm \
    --to=johnstul@us.ibm.com \
    --cc=hector.palacios@digi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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).