public inbox for linux-rt-users@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Mike Galbraith <mgalbraith@suse.de>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: SUSE question wrt RT locking primitives
Date: Fri, 13 Apr 2012 17:47:39 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.2.02.1204131744120.2542@ionos> (raw)
In-Reply-To: <1334328819.13006.24.camel@marge.simpson.net>

On Fri, 13 Apr 2012, Mike Galbraith wrote:

> On Fri, 2012-04-13 at 08:58 -0400, Steven Rostedt wrote: 
> > On Fri, 2012-04-13 at 07:34 +0200, Mike Galbraith wrote:
> 
> > > So that's where the question comes from.  Life would be easier if RT
> > > didn't trigger the Dr. Jeckle -> Mr. Hyde thing.  You know all about
> > > where what happens to which locks, so I'll just snip what I had quoted
> > > and needlessly commented on to keep this as short as possible ;-)
> > 
> > I have no problem with making those non-GPL, as the original stance of
> > -rt back in 2005 was to not have -rt be any different than the vanilla
> > kernel in that regards. But I don't know if that policy changed since
> > then, nor am I the one that has the authority to remove the GPL tags
> > from those functions.
> 
> As timing would have it, Thomas changed to ones that the nVidia driver
> griped about before I even got the query sent.  I just built and ran it,
> it's happy in unmolested form.  Dunno if this will make all RT module
> grumbles go away, but the nVidia ones should be toast.

AFAICT, that should solve all of the RT induced problems.

Feel free to forward my announce mail to those who made you write that
request :)

Thanks,

	tglx

  reply	other threads:[~2012-04-13 15:47 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-14  1:44 [PATCH 1/2] v3.2-rc1-52e4c2a05-rt1 fix for compile break John Kacur
2011-11-14  1:44 ` [PATCH 2/2] Compile error with allmodconfig and CONFIG_PREEMPT_RT_FULL=y John Kacur
2011-11-14 16:51   ` Paul E. McKenney
2011-11-14 17:39     ` John Kacur
2011-11-14 17:57       ` Paul E. McKenney
2011-11-14 20:51       ` Steven Rostedt
2011-11-14 21:07         ` John Kacur
2011-11-15  5:22         ` Mike Galbraith
2011-11-15 12:23           ` Steven Rostedt
2011-11-15 13:27             ` Mike Galbraith
2011-11-15 13:45               ` Mike Galbraith
2011-11-16 14:21               ` Mike Galbraith
2012-04-13  5:34         ` SUSE question wrt RT locking primitives Mike Galbraith
2012-04-13 12:58           ` Steven Rostedt
2012-04-13 14:53             ` Mike Galbraith
2012-04-13 15:47               ` Thomas Gleixner [this message]
2011-11-14 16:50 ` [PATCH 1/2] v3.2-rc1-52e4c2a05-rt1 fix for compile break Paul E. McKenney
2011-11-14 20:57 ` Steven Rostedt

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=alpine.LFD.2.02.1204131744120.2542@ionos \
    --to=tglx@linutronix.de \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=mgalbraith@suse.de \
    --cc=rostedt@goodmis.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