From: Thomas Gleixner <tglx@linutronix.de>
To: Greg KH <greg@kroah.com>
Cc: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
linux-kernel@vger.kernel.org, linux-rt@pengutronix.de,
"Ian Abbott" <abbotti@mev.co.uk>,
"Frank Mori Hess" <fmhess@users.sourceforge.net>
Subject: Re: [PATCH -rt] disable building all staging drivers
Date: Tue, 23 Jun 2009 17:39:36 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.00.0906231737580.2767@localhost.localdomain> (raw)
In-Reply-To: <20090623151701.GD30806@kroah.com>
On Tue, 23 Jun 2009, Greg KH wrote:
> > But, after looking into that code I really have to ask you whether you
> > are serious about fixing it instead of rewriting it from scratch and
> > just keep the code as is for reference to the hardware details.
>
> That is exactly what the code is there for. There are other groups
> rewriting these drivers from scratch, and hopefully they will be done in
> a kernel release or two and then these drivers can go away.
Ok. I just wondered :)
> If, in the mean time, you don't want them to be built for -rt kernels,
> just send me a Kconfig patch for the individual drivers, not for the
> whole of the staging tree.
Sure, I can mark them individually broken on RT in the -rt patch
itself if we stomp over such issues.
Thanks,
tglx
next prev parent reply other threads:[~2009-06-23 15:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-13 21:38 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
2009-06-23 11:24 ` Thomas Gleixner
2009-06-23 15:17 ` Greg KH
2009-06-23 15:39 ` Thomas Gleixner [this message]
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=alpine.LFD.2.00.0906231737580.2767@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=abbotti@mev.co.uk \
--cc=fmhess@users.sourceforge.net \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt@pengutronix.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
all inboxes | Powered by JetHome®