public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Daniel Walker <dwalker@fifo99.com>
Cc: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	linux-kernel@vger.kernel.org, linux-rt@pengutronix.de,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"Ian Abbott" <abbotti@mev.co.uk>,
	"Frank Mori Hess" <fmhess@users.sourceforge.net>
Subject: Re: [PATCH -rt] disable building all staging drivers
Date: Mon, 22 Jun 2009 13:51:50 -0700	[thread overview]
Message-ID: <20090622205150.GA10360@kroah.com> (raw)
In-Reply-To: <1245693964.32124.52.camel@desktop>

On Mon, Jun 22, 2009 at 11:06:04AM -0700, Daniel Walker wrote:
> On Mon, 2009-06-22 at 10:19 -0700, Greg KH wrote:
> > On Mon, Jun 22, 2009 at 05:15:15PM +0200, Uwe Kleine-König wrote:
> > > Hi Greg,
> > > 
> > > On Mon, Jun 15, 2009 at 01:00:44AM +0200, Uwe Kleine-König wrote:
> > > > On Sun, Jun 14, 2009 at 04:28:02AM -0700, Greg KH wrote:
> > > > > On Sat, Jun 13, 2009 at 11:38:38PM +0200, Uwe Kleine-König wrote:
> > > > > > I know that at least COMEDI and RT2870 are broken with -rt,
> > > > > 
> > > > > I didn't know this, has anyone sent me a bug report?  What in -rt causes
> > > > > these drivers to break?
> > > > > 
> > > > > > but Thomas requested disabling all of staging.  He's the maintainer.
> > > > > 
> > > > > This seems like a patch to ensure that the staging drivers never get a
> > > > > chance to be fixed for any potential -rt issues.  How about just sending
> > > > > me bug reports instead?
> > > > I cannot reproduce the failure I saw for RT2870 at the moment.
> > > OK, hit again:
> > > 
> > > 17:02:43 E: ERROR: "there_is_no_init_MUTEX_LOCKED_for_RT_semaphores" [drivers/staging/rt2870/rt2870sta.ko] undefined!
> > 
> > What needs to be done in the rt2870 driver to resolve this issue?
> 
> The semaphore needs to be converted to a completion. Or the code needs
> to be re-worked so it can use a mutex.

Patches gladly accepted :)

thanks,

greg k-h

  reply	other threads:[~2009-06-22 20:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-13 21:38 [PATCH -rt] disable building all staging drivers Uwe Kleine-König
2009-06-14 11:28 ` Greg KH
2009-06-14 12:34   ` Thomas Gleixner
2009-06-14 23:00   ` Uwe Kleine-König
2009-06-14 23:04     ` Greg KH
2009-06-22 15:15     ` Uwe Kleine-König
2009-06-22 17:19       ` Greg KH
2009-06-22 18:06         ` Daniel Walker
2009-06-22 20:51           ` Greg KH [this message]
2009-06-23 11:24         ` Thomas Gleixner
2009-06-23 15:17           ` Greg KH
2009-06-23 15:39             ` Thomas Gleixner
2009-09-07 16:20       ` [RT + staging] buildfailures Uwe Kleine-König
2009-09-08 18:11         ` Greg KH

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=20090622205150.GA10360@kroah.com \
    --to=greg@kroah.com \
    --cc=abbotti@mev.co.uk \
    --cc=dwalker@fifo99.com \
    --cc=fmhess@users.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt@pengutronix.de \
    --cc=tglx@linutronix.de \
    --cc=u.kleine-koenig@pengutronix.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