public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Sven-Thorsten Dietrich <sven@thebigcorporation.com>
Cc: RT Users List <linux-rt-users@vger.kernel.org>,
	LKML <Linux-kernel@vger.kernel.org>,
	Peter Williams <pwil3058@bigpond.net.au>
Subject: Re: [PATCH RT] - trivial branch in scheduler.
Date: Fri, 24 Aug 2007 10:32:22 +0200	[thread overview]
Message-ID: <20070824083222.GA22260@elte.hu> (raw)
In-Reply-To: <1187943548.16573.10.camel@sx.thebigcorporation.com>


* Sven-Thorsten Dietrich <sven@thebigcorporation.com> wrote:

> 
> Hi Ingo,
> 
> the trivial code is in various RT patches as well as in 2.6.23-rc git's
> scheduler.
> 
> Thanks
> 
> Sven
> 
> Remove trivial conditional branch in Linux RT CFS 
> scheduler's can_migrate_task function.
> 
> signed-off-by: Sven-Thorsten Dietrich <sven@thebigcorporation.com>

thanks, applied.

	Ingo

      reply	other threads:[~2007-08-24  8:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-24  8:19 [PATCH RT] - trivial branch in scheduler Sven-Thorsten Dietrich
2007-08-24  8:32 ` 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=20070824083222.GA22260@elte.hu \
    --to=mingo@elte.hu \
    --cc=Linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=pwil3058@bigpond.net.au \
    --cc=sven@thebigcorporation.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