public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: 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: Sun, 14 Jun 2009 16:04:00 -0700	[thread overview]
Message-ID: <20090614230400.GA12366@kroah.com> (raw)
In-Reply-To: <20090614230044.GA21624@pengutronix.de>

On Mon, Jun 15, 2009 at 01:00:44AM +0200, Uwe Kleine-König wrote:
> Hi Greg,
> 
> 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?
> COMEDI has:
> 
>   CC [M]  drivers/staging/comedi/comedi_fops.o
> In file included from drivers/staging/comedi/comedidev.h:40,
>                  from drivers/staging/comedi/comedi_fops.c:45:
> drivers/staging/comedi/interrupt.h:27: error: conflicting types for ‘irqreturn_t’
> include/linux/irqreturn.h:14: error: previous declaration of ‘irqreturn_t’ was here
> In file included from drivers/staging/comedi/comedidev.h:40,
>                  from drivers/staging/comedi/comedi_fops.c:45:
> drivers/staging/comedi/interrupt.h:30:1: warning: "IRQ_RETVAL" redefined
> In file included from include/linux/interrupt.h:10,
>                  from drivers/staging/comedi/interrupt.h:22,
>                  from drivers/staging/comedi/comedidev.h:40,
>                  from drivers/staging/comedi/comedi_fops.c:45:
> include/linux/irqreturn.h:15:1: warning: this is the location of the previous definition
> make[3]: *** [drivers/staging/comedi/comedi_fops.o] Error 1
> make[2]: *** [drivers/staging/comedi] Error 2
> make[1]: *** [drivers/staging] Error 2
> make: *** [drivers] Error 2

This should be resolved with the linux-next tree, right?  There are a
few hundred staging patches in there that fix a lot of issues.  They
will all go to Linus in a day or so.

thanks,

greg k-h

  reply	other threads:[~2009-06-14 23:09 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 [this message]
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
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=20090614230400.GA12366@kroah.com \
    --to=greg@kroah.com \
    --cc=abbotti@mev.co.uk \
    --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