From: Robert Love <rml@tech9.net>
To: "Dieter Nützel" <Dieter.Nuetzel@hamburg.de>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH] preemptive kernel
Date: 24 Jan 2002 14:11:57 -0500 [thread overview]
Message-ID: <1011899538.1194.1.camel@phantasy> (raw)
In-Reply-To: <20020124153123Z288377-13996+11264@vger.kernel.org>
In-Reply-To: <20020124153123Z288377-13996+11264@vger.kernel.org>
On Thu, 2002-01-24 at 10:31, Dieter Nützel wrote:
> Hello Robert,
>
> can you please redo for O(1)-J6 (2.4.18-pre7) or is nothing changed?
As Ingo and Tom pointed out, its a trivial reject, but I've gone ahead
and updated the 2.4 patches to 2.4.18-pre7 and 2.4.18-pre7-J6:
ftp.kernel.org/pub/linux/kernel/people/rml/preempt-kernel/v2.4/
My SMP Athlon survived a stress run over night on 2.5.3-pre4-preempt.
Excellent.
Robert Love
next prev parent reply other threads:[~2002-01-24 19:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-24 15:31 [PATCH] preemptive kernel Dieter Nützel
2002-01-24 15:55 ` Tom Rini
2002-01-24 17:57 ` Ingo Molnar
2002-01-24 16:05 ` Tom Rini
2002-01-24 18:04 ` Ingo Molnar
2002-01-24 19:11 ` Robert Love [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-01-24 9:39 Robert Love
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=1011899538.1194.1.camel@phantasy \
--to=rml@tech9.net \
--cc=Dieter.Nuetzel@hamburg.de \
--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