public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: John Stultz <john.stultz@linaro.org>
To: lkml <linux-kernel@vger.kernel.org>
Cc: John Stultz <john.stultz@linaro.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Prarit Bhargava <prarit@redhat.com>,
	Richard Cochran <richardcochran@gmail.com>,
	Ingo Molnar <mingo@kernel.org>,
	Christopher Hall <christopher.s.hall@intel.com>
Subject: [PATCH 0/2][GIT PULL] Timekeeping updates to tip/timers/core for 4.6
Date: Fri, 26 Feb 2016 19:14:12 -0800	[thread overview]
Message-ID: <1456542854-22104-1-git-send-email-john.stultz@linaro.org> (raw)

Hey Thomas, Ingo,
  Here's my somewhat truncated queue for 4.6. I was hoping to
get the cross-timestamp patchset from Christopher sent along,
but he's got some last minute changes to address feedback from
Andy, so I'm holding off.

If the response is good for that last change, I may try to send
another set with those changes next week, but we're cutting it
fairly close to -rc6, so I'll check with you before doing so.

So.. two tiny cleanup fixes is all for now.

Boring is good, right?

Let me know if you have any thoughts or objections.

thanks
-john


The following changes since commit 18558cae0272f8fd9647e69d3fec1565a7949865:

  Linux 4.5-rc4 (2016-02-14 13:05:20 -0800)

are available in the git repository at:

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

for you to fetch changes up to ea23c1da598bfd361af5cd769e292a9667ecb7ab:

  jiffies: use CLOCKSOURCE_MASK instead of constant (2016-02-26 19:05:25 -0800)

----------------------------------------------------------------
Alexander Kuleshov (2):
      clocksource: introduce clocksource_freq2mult()
      jiffies: use CLOCKSOURCE_MASK instead of constant

 include/linux/clocksource.h | 45 +++++++++++++++++++--------------------------
 kernel/time/jiffies.c       |  2 +-
 2 files changed, 20 insertions(+), 27 deletions(-)



Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Prarit Bhargava <prarit@redhat.com>
Cc: Richard Cochran <richardcochran@gmail.com>
Cc: Ingo Molnar <mingo@kernel.org>
Cc: Christopher Hall <christopher.s.hall@intel.com>

Alexander Kuleshov (2):
  clocksource: introduce clocksource_freq2mult()
  jiffies: use CLOCKSOURCE_MASK instead of constant

 include/linux/clocksource.h | 45 +++++++++++++++++++--------------------------
 kernel/time/jiffies.c       |  2 +-
 2 files changed, 20 insertions(+), 27 deletions(-)

-- 
1.9.1

             reply	other threads:[~2016-02-27  3:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-27  3:14 John Stultz [this message]
2016-02-27  3:14 ` [PATCH 1/2] clocksource: introduce clocksource_freq2mult() John Stultz
2016-02-27  8:00   ` [tip:timers/core] clocksource: Introduce clocksource_freq2mult() tip-bot for Alexander Kuleshov
2016-02-27  3:14 ` [PATCH 2/2] jiffies: use CLOCKSOURCE_MASK instead of constant John Stultz
2016-02-27  8:00   ` [tip:timers/core] jiffies: Use " tip-bot for Alexander Kuleshov
2016-02-27  7:50 ` [PATCH 0/2][GIT PULL] Timekeeping updates to tip/timers/core for 4.6 Thomas Gleixner
2016-02-27  7:52 ` Thomas Gleixner

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=1456542854-22104-1-git-send-email-john.stultz@linaro.org \
    --to=john.stultz@linaro.org \
    --cc=christopher.s.hall@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=prarit@redhat.com \
    --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