From: Robin Gilks <robin.gilks@tait.co.nz>
To: linuxppc mail list <linuxppc-embedded@lists.linuxppc.org>
Subject: lowlat & preeempt
Date: Tue, 17 Jun 2003 16:06:29 +1200 [thread overview]
Message-ID: <3EEE93C5.4090302@tait.co.nz> (raw)
Greetings
With the recent release of 2.4.21 I see many patches have been swept up
and incorporated. No sign of the low latency & preemption patches though
(not really suprising in a stable series) but does anyone have a set of
patches for this new tree for ppc only?
Many thanks.
--
Robin Gilks
Senior Design Engineer Phone: (+64)(3) 357 1569
Tait Electronics Fax : (+64)(3) 359 4632
PO Box 1645 Christchurch Email : robin.gilks@tait.co.nz
New Zealand
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2003-06-17 4:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-17 4:06 Robin Gilks [this message]
2003-06-17 5:34 ` lowlat & preeempt Marius Groeger
2003-06-17 6:58 ` Eugene Surovegin
2003-06-17 7:15 ` Marius Groeger
2003-06-17 7:25 ` Eugene Surovegin
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=3EEE93C5.4090302@tait.co.nz \
--to=robin.gilks@tait.co.nz \
--cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).