mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [GIT pull] timer changes for 3.18
Date: Thu, 9 Oct 2014 08:23:27 +0200	[thread overview]
Message-ID: <20141009062327.GA19598@gmail.com> (raw)
In-Reply-To: <20141008223623.GB21582@lerouge>


* Frederic Weisbecker <fweisbec@gmail.com> wrote:

> On Wed, Oct 08, 2014 at 05:54:49PM -0400, Linus Torvalds wrote:
> > On Wed, Oct 8, 2014 at 2:12 PM, Thomas Gleixner <tglx@linutronix.de> wrote:
> > >
> > > please pull the latest timers-core-for-linus git tree from:
> > >
> > >    git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git timers-core-for-linus
> > >
> > > Nothing really exciting this time:
> > >
> > >  - A few fixlets in the NOHZ code
> > 
> > .. but apparently *still* not the fixes from Frederic for the 
> > issue that people are complaining about killing their 
> > machines in 3.17.
> > 
> > WTF? What happened to those?
> 
> Thomas just pulled these in -tip today. I'm pretty sure he 
> plans to make a 2nd timers pile after this one during the merge 
> window. We just found a non-trivial conflict in my branch 
> against the RCU tree so this probably needs a bit of last 
> minute adjustment and testing.

Thomas won't be around until next week, I'll send these fixes 
later today.

Thanks,

	Ingo

      reply	other threads:[~2014-10-09  6:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-08 18:12 Thomas Gleixner
2014-10-08 21:54 ` Linus Torvalds
2014-10-08 22:36   ` Frederic Weisbecker
2014-10-09  6:23     ` Ingo Molnar [this message]

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=20141009062327.GA19598@gmail.com \
    --to=mingo@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=fweisbec@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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

Powered by JetHome