linux-kernel - Re: (Short?) merge window reminder

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, 24 May 2011 16:46:27 +0100
From:	Ralf Baechle <ralf@...ux-mips.org>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	Jacek Luczak <difrost.kernel@...il.com>,
	Jan Engelhardt <jengelh@...ozas.de>,
	linux-arch@...r.kernel.org, "Ted Ts'o" <tytso@....edu>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	DRI <dri-devel@...ts.freedesktop.org>,
	"H. Peter Anvin" <hpa@...or.com>,
	linux-fsdevel <linux-fsdevel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: (Short?) merge window reminder

On Tue, May 24, 2011 at 03:43:48PM +0100, Alan Cox wrote:

> Can we drop most of MCA, EISA and ISA bus if we are going to have a big
> version change ? A driver spring clean is much overdue and it's all in
> git in case someone wishes to sneak out at midnight and bring some crawly
> horror back from the dead.

Dunno about MCA but I doubt we can kill all of (E)ISA. i8253, i8259 and a
few others still refuse hard to die.  

Is it worth to setup a system to track success / failure reports for
drivers and ditch drivers once there are no success reports for a driver
for too long?  It may not be a good idea - people tend not report success
much more rarely than failure.

(On that matter, I wonder if there are 5.25" USB floppy drives ...)

  Ralf
--
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/