From: Nick Piggin <piggin@cyberone.com.au>
To: Jose Luis Alarcon Sanchez <jlalarcon@chevy.zzn.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Nick's scheduler policy v13
Date: Mon, 08 Sep 2003 03:48:29 +1000 [thread overview]
Message-ID: <3F5B6F6D.8020002@cyberone.com.au> (raw)
In-Reply-To: <049BFF88F93883E4F94039457A2A2AC3@jlalarcon.chevy.zzn.com>
Jose Luis Alarcon Sanchez wrote:
> Hi Nick.
>
> I wanna ask you what are the differences beetween your
>"scheduler policy" and "rollup" patches.
>
> I have installed your last rollup.patch, i must install
>too this scheduler policy version 13? or not?.
>
Hi Jose,
My scheduler policy patches are now just a rollup of a few different
things. Sorry for the confusing naming of the attachments.
This one will replace the last, applying to plain 2.6.0-test4.
next prev parent reply other threads:[~2003-09-07 17:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-07 17:28 [PATCH] Nick's scheduler policy v13 Jose Luis Alarcon Sanchez
2003-09-07 17:48 ` Nick Piggin [this message]
[not found] <1062938059.3485.2.camel@pilot.stavtrup-st.dk>
2003-09-07 17:13 ` Nick Piggin
2003-09-07 17:59 ` Nick Piggin
2003-09-07 18:15 ` Mike Galbraith
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=3F5B6F6D.8020002@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=jlalarcon@chevy.zzn.com \
--cc=linux-kernel@vger.kernel.org \
/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