From: Maarten Lankhorst <m.b.lankhorst@gmail.com>
To: Sven-Thorsten Dietrich <thebigcorporation@gmail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: [ANNOUNCE] 3.0-rt1
Date: Sat, 23 Jul 2011 22:02:14 +0200 [thread overview]
Message-ID: <4E2B28C6.2050806@gmail.com> (raw)
In-Reply-To: <3E6C10F4-B619-4DBF-9EF3-F7B3EDF53608@gmail.com>
Hi Dietrich,
On 07/23/2011 08:57 PM, Sven-Thorsten Dietrich wrote:
> On Jul 22, 2011, at 6:05 PM, Maarten Lankhorst wrote:
>
>> On 07/22/2011 10:37 PM, Thomas Gleixner 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
>> Sweet, works here :)
>>
>> Only the nvidia driver fails to build because of rtmutex and migrate enable/disable being GPL only, you might want to reconsider the GPL only status of them.
> Can you reconsider using nVidia ?
You see, I've been living two lives. In one life, I'm Maarten B Lankhorst. I work on wine, and since a week or so I've been working on nouveau. And I... help fix kernel bugs that I'm affected by. My other life is in computers, where I go by the hacker alias ROFLGAMER, participating actively in computer simulated environments and am playing graphic intensive games using wine. Unfortunately when I do that I just want things to work, nouveau keeps getting better all the time, but wine's d3d is a lot more tested with the nvidia blob. ;)
~Maarten
next prev parent reply other threads:[~2011-07-23 20:02 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-22 20:37 [ANNOUNCE] 3.0-rt1 Thomas Gleixner
2011-07-22 21:07 ` Kim Leyendecker
2011-07-22 21:16 ` Thomas Gleixner
2011-07-23 5:51 ` Kim Leyendecker
2011-07-22 22:51 ` Rolando Martins
2011-07-23 7:31 ` Thomas Gleixner
2011-07-23 9:38 ` Rolando Martins
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 [this message]
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=4E2B28C6.2050806@gmail.com \
--to=m.b.lankhorst@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=thebigcorporation@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.