linux-kernel - Re: [PATCH -rt] disable building all staging drivers

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 23 Jun 2009 17:39:36 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Greg KH <greg@...ah.com>
cc:	Uwe Kleine-König 
	<u.kleine-koenig@...gutronix.de>, linux-kernel@...r.kernel.org,
	linux-rt@...gutronix.de, Ian Abbott <abbotti@....co.uk>,
	Frank Mori Hess <fmhess@...rs.sourceforge.net>
Subject: Re: [PATCH -rt] disable building all staging drivers

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/