public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Shawn Bohrer <sbohrer@rgmadvisors.com>,
	Ingo Molnar <mingo@elte.hu>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched_rt: Migrate equal priority tasks to available CPUs
Date: Wed, 14 Sep 2011 17:27:49 +0200	[thread overview]
Message-ID: <1316014069.5040.23.camel@twins> (raw)
In-Reply-To: <1315947117.26295.22.camel@gandalf.stny.rr.com>

On Tue, 2011-09-13 at 16:51 -0400, Steven Rostedt wrote:
> I ran a version with your patch and I could not trigger the bug. I
> consider this a real regression.
> 
> Acked-by: Steven Rostedt <rostedt@goodmis.org> 

Thanks Shawn, Steven.

Queued with a CC to stable for 37+.

      reply	other threads:[~2011-09-14 15:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-12 14:28 [PATCH] sched_rt: Migrate equal priority tasks to available CPUs Shawn Bohrer
2011-09-13 13:05 ` Steven Rostedt
2011-09-13 16:27   ` Shawn Bohrer
2011-09-13 20:06     ` Shawn Bohrer
2011-09-13 20:51       ` Steven Rostedt
2011-09-14 15:27         ` Peter Zijlstra [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=1316014069.5040.23.camel@twins \
    --to=peterz@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.org \
    --cc=sbohrer@rgmadvisors.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