LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Ingo Molnar <mingo@elte.hu>,
	Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com>,
	Dhaval Giani <dhaval@linux.vnet.ibm.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/2] for sched-devel.git
Date: Fri, 15 Feb 2008 12:18:20 +0100	[thread overview]
Message-ID: <20080215111819.978881000@chello.nl> (raw)

Hi Ingo,

Would you stick these into sched-devel.

The first patch should address the latency isolation issue. While the second
rectifies a massive brainfart :-)




             reply	other threads:[~2008-02-15 11:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-15 11:18 Peter Zijlstra [this message]
2008-02-15 11:18 ` [PATCH 1/2] sched: fair: virtual deadline scheduling Peter Zijlstra
2008-02-15 11:18 ` [PATCH 2/2] sched: fair: fix calc_delta_asym Peter Zijlstra
2008-02-17 16:35 ` [PATCH 0/2] for sched-devel.git Ingo Molnar

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=20080215111819.978881000@chello.nl \
    --to=a.p.zijlstra@chello.nl \
    --cc=dhaval@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=vatsa@linux.vnet.ibm.com \
    --subject='Re: [PATCH 0/2] for sched-devel.git' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).