All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	LKML <linux-kernel@vger.kernel.org>,
	Archs <linux-arch@vger.kernel.org>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Rik van Riel <riel@redhat.com>, Huiqingding <huding@redhat.com>
Subject: Re: [GIT PULL v2] timers updates for 3.15
Date: Fri, 14 Mar 2014 09:36:52 +0100	[thread overview]
Message-ID: <20140314083652.GA22913@gmail.com> (raw)
In-Reply-To: <20140313153301.GA25296@localhost.localdomain>


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

> So I propose you something even more simple. The choice of 
> tip:timers/core as a base was actually just about topic. But there 
> is no dependency on it. (And actually sched/core would have been a 
> better choice for a base if any).
> 
> So in order to fix the conflict and minimize the dependencies, I 
> just rebased the patches on top of tip:core/locking only. No merge 
> on top of that. It seems to work pretty well.
> 
> The pullable result is in sched/cputime on my tree. Let me know if 
> that's ok for you.

Yeah, that sounds excellent. Thomas, you might want to keep this in a 
sparate branch from timers/core though. We still have timers/nohz for 
example.

Thanks,

	Ingo

      reply	other threads:[~2014-03-14  8:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-12 16:36 [GIT PULL v2] timers updates for 3.15 Frederic Weisbecker
2014-03-13 11:05 ` Ingo Molnar
2014-03-13 15:33   ` Frederic Weisbecker
2014-03-14  8:36     ` 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=20140314083652.GA22913@gmail.com \
    --to=mingo@kernel.org \
    --cc=fweisbec@gmail.com \
    --cc=huding@redhat.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=peterz@infradead.org \
    --cc=riel@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.