All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	fweisbec@gmail.com, mingo@kernel.org,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: Another RCU trace. (3.10-rc5)
Date: Tue, 18 Jun 2013 10:40:20 -0400	[thread overview]
Message-ID: <20130618144020.GB1313@redhat.com> (raw)
In-Reply-To: <20130618095821.GJ3204@twins.programming.kicks-ass.net>

On Tue, Jun 18, 2013 at 11:58:21AM +0200, Peter Zijlstra wrote:

 > > Peter, Are you going to take the preempt_schedule_context() patch?
 > 
 > I have it queued, I just seem to have some problems locating Ingo to
 > stuff patches into -tip :/
 > 
 > Will continue prodding.. Ingo if you're reading! :-)

There's a bunch of other stuff in tip pending pushing to Linus too,
including a bunch of fixes in timers/urgent that have been there
over a month.

Ingo hasn't posted since the 3rd, maybe he's sick/on vacation.
Does anyone else do pushes from tip->Linus ?  tglx ?

	Dave


  reply	other threads:[~2013-06-18 14:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-10 19:51 Another RCU trace. (3.10-rc5) Dave Jones
2013-06-10 20:33 ` Paul E. McKenney
2013-06-10 21:01   ` Dave Jones
2013-06-10 21:16     ` Steven Rostedt
2013-06-18  9:58       ` Peter Zijlstra
2013-06-18 14:40         ` Dave Jones [this message]
2013-06-18 17:32           ` Peter Zijlstra
2013-06-10 21:18     ` Paul E. McKenney
2013-06-10 21:37       ` Steven Rostedt
2013-06-10 21:54         ` Dave Jones
2013-06-10 22:10           ` Paul E. McKenney
2013-06-10 22:25             ` Steven Rostedt
2013-06-10 22:10           ` Steven Rostedt
2013-06-10 20:38 ` Steven Rostedt

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=20130618144020.GB1313@redhat.com \
    --to=davej@redhat.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --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.