From: Tim Blechmann <tim@klingt.org>
To: linux-rt-users@vger.kernel.org
Subject: Re: Nvidia patches for 2.6.33-rt?
Date: Tue, 02 Mar 2010 10:47:57 +0100 [thread overview]
Message-ID: <hmimsd$jmt$1@dough.gmane.org> (raw)
In-Reply-To: 20100302101613.10143wu0pseylo3k@neverland.cauwe.org
> I don't think the problem is rt-related, but generally to the vanilla
> version.
actually, it is ... atomic_spinlock_t was renamed to raw_spinlock_t, and
apparently semaphore_init isn't there any more ...
the first issue is trivial, for the second, i didn't follow the rt patches
closely enough ...
tim
--
tim@klingt.org
http://tim.klingt.org
Your mind will answer most questions if you learn to relax and wait
for the answer.
William S. Burroughs
next prev parent reply other threads:[~2010-03-02 9:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-02 8:59 Nvidia patches for 2.6.33-rt? Ng Oon-Ee
2010-03-02 9:16 ` Xavier Miller
2010-03-02 9:47 ` Tim Blechmann [this message]
2010-03-03 12:16 ` Jonathan Schmidt
2010-03-04 3:20 ` Ng Oon-Ee
2010-03-04 8:42 ` Uwe Kleine-König
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='hmimsd$jmt$1@dough.gmane.org' \
--to=tim@klingt.org \
--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).