public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "J.A. Magallon" <jamagallon@able.es>
To: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>
Subject: Re: 0(1)-patch, where did it go?
Date: Wed, 10 Apr 2002 23:49:55 +0200	[thread overview]
Message-ID: <20020410214955.GA1752@werewolf.able.es> (raw)
In-Reply-To: <20020409221631.GA1742@werewolf.able.es> <2033233415.1018391675@[10.10.2.3]>


On 2002.04.10 Martin J. Bligh wrote:
>> You can get an up-to-date version in the 2.4.19-pre6-jam1 patcset in
>> 
>> http://giga.cps.unizar.es/~magallon/linux/kernel/
>
>Do you have a version of this broken out as a seperate patch 
>anywhere? There seem to have been updates to the O(1) scheduler 
>in 2.5 since the K3 version of the scheduler, but I've not seen
>any new version of the 2.4 version of the patch ...
>

The patch in that location is split in pieces, but it patches on top of
all the previous patches in the set. I could make it patch cleanly on
plain 2.4.19-pre6, but if there have been changes in the O1 scheduler
it would be better that Ingo backported them to 2.4 if he has the
time.

-- 
J.A. Magallon                           #  Let the source be with you...        
mailto:jamagallon@able.es
Mandrake Linux release 8.3 (Cooker) for i586
Linux werewolf 2.4.19-pre6-jam1 #1 SMP Sun Apr 7 00:50:05 CEST 2002 i686

  reply	other threads:[~2002-04-10 21:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-09 20:51 0(1)-patch, where did it go? listmail
2002-04-09 21:11 ` J Sloan
2002-04-09 22:16 ` J.A. Magallon
2002-04-10  5:34   ` Martin J. Bligh
2002-04-10 21:49     ` J.A. Magallon [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-11  3:27 Dieter Nützel
2002-04-11  3:30 ` Robert Love
2002-04-11  3:44   ` Dieter Nützel
2002-04-11  5:58 ` KELEMEN Peter

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=20020410214955.GA1752@werewolf.able.es \
    --to=jamagallon@able.es \
    --cc=Martin.Bligh@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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