From: Lee Revell <rlrevell@joe-job.com>
To: mjc@unre.st
Cc: linux-kernel@vger.kernel.org
Subject: Re: Updated realtime-preempt documentation
Date: Sat, 30 Apr 2005 02:11:27 -0400 [thread overview]
Message-ID: <1114841487.8636.29.camel@mindpipe> (raw)
In-Reply-To: <2119.66.176.128.144.1114839452.squirrel@mail.unre.st>
On Sat, 2005-04-30 at 01:37 -0400, mjc@unre.st wrote:
> Hey all,
>
> I've been following Ingo Molnar and friends' lovely realtime-preempt
> patchset. I'm curious, though, the only piece of documentation I've
> found is
> http://people.redhat.com/mingo/realtime-preempt/older/ANNOUNCE-voluntary-preempt
> which is, indeed, quite old. Is anyone planning on updating this in
> the near future or is it in too much flux? Should I try and make heads or
> tails of the code first?
I think it's changing too fast for anyone to have bothered to document
it yet.
But, you could make some pretty good documentation based on the LKML
discussions of RT preemption, especially Ingo's posts.
Lee
next prev parent reply other threads:[~2005-04-30 6:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-30 5:37 Updated realtime-preempt documentation mjc
2005-04-30 6:11 ` Lee Revell [this message]
2005-04-30 14:28 ` Daniel Walker
2005-04-30 18:17 ` Lee Revell
2005-04-30 14:22 ` Daniel Walker
2005-04-30 15:39 ` john cooper
2005-04-30 20:31 ` Jonathan Corbet
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=1114841487.8636.29.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjc@unre.st \
/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