linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Galbraith <umgwanakikbuti@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Borislav Petkov <bp@alien8.de>,
	Peter Zijlstra <peterz@infradead.org>, x86-ml <x86@kernel.org>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: rc5+tip/master: Marking clocksource 'tsc' as unstable because the skew is too large:
Date: Thu, 30 Jun 2016 16:29:52 +0200	[thread overview]
Message-ID: <1467296992.9949.43.camel@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.11.1606301541590.3707@nanos>

On Thu, 2016-06-30 at 15:43 +0200, Thomas Gleixner wrote:
> On Thu, 30 Jun 2016, Mike Galbraith wrote:
> > 
> > Lunch rendered me (yawn) comatose, so I'm a bit late, but sent.
> 
> Patch below should fix the issue - the timer one, not yours :)

<twiddle>

Box should have griped by now.. yup, all better.

	-Mike

(mine isn't a wart, it's a.. somewhat noisy [90 dB] beauty mark)

  parent reply	other threads:[~2016-06-30 14:30 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-27 20:06 rc5+tip/master: Marking clocksource 'tsc' as unstable because the skew is too large: Borislav Petkov
2016-06-29 17:16 ` Borislav Petkov
2016-06-30  7:57   ` Mike Galbraith
2016-06-30  8:41     ` Thomas Gleixner
2016-06-30  9:15       ` Mike Galbraith
2016-06-30  9:42         ` Thomas Gleixner
2016-06-30  9:49           ` Mike Galbraith
2016-06-30 10:24             ` Thomas Gleixner
2016-06-30 13:39               ` Mike Galbraith
2016-06-30 13:43                 ` Thomas Gleixner
2016-06-30 14:27                   ` Borislav Petkov
2016-06-30 14:29                   ` Mike Galbraith [this message]
2016-06-30 20:11                   ` Richard Cochran
2016-06-30 10:29             ` Mike Galbraith
2016-06-30 10:31               ` Thomas Gleixner
2016-06-30  8:40   ` Thomas Gleixner
2016-06-30  9:49     ` Borislav Petkov

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=1467296992.9949.43.camel@gmail.com \
    --to=umgwanakikbuti@gmail.com \
    --cc=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /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).