linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dennis Borgmann <dennis.borgmann@googlemail.com>
To: linux-rt-users@vger.kernel.org
Subject: patchset still being developed?
Date: Fri, 10 Dec 2010 14:22:09 +0100	[thread overview]
Message-ID: <4D022981.20606@googlemail.com> (raw)

Hello rt-users!

Is the CONFIG PREEMPT RT Patch still developed? So far I canot find any
newer patchset than the one for kernel 2.6.33.7 on
http://www.kernel.org/pub/linux/kernel/projects/rt/ but what I can find
is submissions to the linux kernel related to PREEMPT stuff in the
Changelog of recent kernels.

Does this mean, that with current kernels (starting 2.6.34) no more
patching is needed and a Kernel can be configured to do realtime
preemption without patches?

If so, an update on the mainpage of the wiki would be nice...

Kind regards,
Dennis

             reply	other threads:[~2010-12-10 13:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-10 13:22 Dennis Borgmann [this message]
2010-12-10 14:43 ` patchset still being developed? Dennis Borgmann
     [not found]   ` <02c401cb987a$05b01910$11104b30$@pont@sdcsystems.com>
2010-12-10 14:54     ` Dennis Borgmann

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=4D022981.20606@googlemail.com \
    --to=dennis.borgmann@googlemail.com \
    --cc=linux-rt-users@vger.kernel.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).