From: Tabris <tabris@sbcglobal.net>
To: Robert Love <rml@tech9.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch] updated preemptive kernel for 2.4.21
Date: Sat, 21 Jun 2003 20:18:56 -0400 [thread overview]
Message-ID: <200306212018.57045.tabris@sbcglobal.net> (raw)
> I put an updated preempt-kernel patch up at:
>
> http://www.kernel.org/pub/linux/kernel/people/rml/preempt-kernel/v2.4/
>
> The patch is a rediff to 2.4.21, but also contains a number of fixes
> for preempt-unsafe code -- both longstanding issues and new problems
> arising from the 2.4.21 development cycle. Thanks to Joe Korty and
> various folks at MontaVista for a lot of the fixes.
>
> Please give it a whirl. Or, even better, switch to 2.5
>
> Enjoy,
>
> Robert Love
>
May we look forward to a 2.4.21-ac patch?
--
tabris
-
Research, n.:
Consider Columbus:
He didn't know where he was going.
When he got there he didn't know where he was.
When he got back he didn't know where he had been.
And he did it all on someone else's money.
next reply other threads:[~2003-06-22 0:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-22 0:18 Tabris [this message]
2003-06-22 0:21 ` [patch] updated preemptive kernel for 2.4.21 Robert Love
-- strict thread matches above, loose matches on Subject: below --
2003-06-18 0:46 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=200306212018.57045.tabris@sbcglobal.net \
--to=tabris@sbcglobal.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.net \
/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