linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rolando Martins <rolando.martins@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
	linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: [ANNOUNCE] 3.0-rt1
Date: Fri, 22 Jul 2011 23:51:21 +0100	[thread overview]
Message-ID: <CABcS5h01jpOSKcKtrJ65AqNNQDCAOutQADAE_pcRp-MPBoO-VA@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.02.1107222203400.2702@ionos>

Thanks for the great work!

Is it possible to have RT_GROUP_SCHED and PREEMPT_RT_FULL?

Thanks.
Rolando Martins


On Fri, Jul 22, 2011 at 9:37 PM, Thomas Gleixner <tglx@linutronix.de> wrote:
> Dear RT Folks,
>
> I'm pleased to announce the 3.0-rt1 release.
>
> Changes versus 3.0-rc7-rt0:
>
>  * Update to Linus final 3.0 release
>
>  * RTC bugfixes (scheduled for mainline/stable)
>
>  * Long standing (rt only) timer_list bug (see
>    timers-avoid-the-base-null-otptimization-on-rt.patch in the split
>    out quilt queue)
>
>  * Minor non exciting fixes all over the place
>
> Known issues:
>
>  * Some weird "console=..." commandline + config dependent
>    interactions which have been not yet investigated down to their
>    root cause. Result in a boot hang. YMMV
>
> Patch against 3.0 can be found here:
>
>  http://www.kernel.org/pub/linux/kernel/projects/rt/patch-3.0-rt1.patch.bz2
>
> The split quilt queue is available at:
>
>  http://www.kernel.org/pub/linux/kernel/projects/rt/patches-3.0-rt1.tar.bz2
>
> Thanks,
>
>        tglx
> --
> To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

  reply	other threads:[~2011-07-22 22:51 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-22 20:37 [ANNOUNCE] 3.0-rt1 Thomas Gleixner
2011-07-22 22:51 ` Rolando Martins [this message]
2011-07-23  7:31   ` Thomas Gleixner
2011-07-23  9:38     ` Rolando Martins
2011-07-23 10:20       ` Thomas Gleixner
2011-07-23 10:44         ` Peter Zijlstra
2011-07-23 10:47           ` Thomas Gleixner
2011-07-22 23:23 ` Ed Tomlinson
2011-07-23  7:43   ` Thomas Gleixner
2011-07-23  1:05 ` Maarten Lankhorst
2011-07-23 13:34   ` Peter W. Morreale
2011-08-10  5:14     ` Mike Galbraith
2011-08-10  5:28       ` Mike Galbraith
2011-08-10 13:56       ` Peter W. Morreale
     [not found]   ` <3E6C10F4-B619-4DBF-9EF3-F7B3EDF53608@gmail.com>
2011-07-23 20:02     ` Maarten Lankhorst
2011-07-23  7:50 ` Mike Galbraith
2011-07-23  7:53   ` Thomas Gleixner
2011-07-23 14:29 ` Juergen Beisert
2011-07-23 14:52   ` Robin Gareus
2011-07-23 15:00   ` Thomas Gleixner
  -- strict thread matches above, loose matches on Subject: below --
2011-07-21 16:22 [ANNOUNCE] 3.0-rc7-rt0 hermann
2011-07-21 17:35 ` Thomas Gleixner
2011-07-21 17:43   ` Thomas Gleixner
2011-07-23  4:08     ` [ANNOUNCE] 3.0-rt1 hermann
2011-07-23  7:37       ` Thomas Gleixner

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=CABcS5h01jpOSKcKtrJ65AqNNQDCAOutQADAE_pcRp-MPBoO-VA@mail.gmail.com \
    --to=rolando.martins@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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).