mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: John Stultz <john.stultz@linaro.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
	Prarit Bhargava <prarit@redhat.com>,
	Richard Cochran <richardcochran@gmail.com>,
	Ingo Molnar <mingo@kernel.org>,
	Christopher Hall <christopher.s.hall@intel.com>
Subject: Re: [PATCH 0/2][GIT PULL] Timekeeping updates to tip/timers/core for 4.6
Date: Sat, 27 Feb 2016 08:50:58 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.11.1602270849350.3638@nanos> (raw)
In-Reply-To: <1456542854-22104-1-git-send-email-john.stultz@linaro.org>

John,

On Fri, 26 Feb 2016, John Stultz wrote:

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

If it's just the small fixup to address review comments, we still should take
it.
 
> So.. two tiny cleanup fixes is all for now.
> 
> Boring is good, right?

:)

Thanks,

	tglx

  parent reply	other threads:[~2016-02-27  7:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-27  3:14 John Stultz
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 ` Thomas Gleixner [this message]
2016-02-27  7:52 ` [PATCH 0/2][GIT PULL] Timekeeping updates to tip/timers/core for 4.6 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=alpine.DEB.2.11.1602270849350.3638@nanos \
    --to=tglx@linutronix.de \
    --cc=christopher.s.hall@intel.com \
    --cc=john.stultz@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=prarit@redhat.com \
    --cc=richardcochran@gmail.com \
    /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
all inboxes | Powered by JetHome®