linux-kernel - Re: removing existing working drivers via staging

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20091027104524.2cf3f9a5@lxorguk.ukuu.org.uk>
Date:	Tue, 27 Oct 2009 10:45:24 +0000
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	david@...g.hm
Cc:	Stefan Richter <stefanr@...6.in-berlin.de>,
	Ingo Molnar <mingo@...e.hu>, Greg KH <gregkh@...e.de>,
	Bartlomiej Zolnierkiewicz <bzolnier@...il.com>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: removing existing working drivers via staging

> this is exactly the 'wants to get rid of' category I mentioned being 
> concerned about below.

Why are you concerned, its dead, its defunct, nobody cares, nobody uses
it. The same is true of a lot of other junk drivers we have and need to
get rid of.

> I don't know what was decided at the kernel summit where this was 
> discussed, how easy is it supposed to be to drop drivers out of the 
> kernel?

If there is someone with the hardware its a trivial git command to put it
back and they can then maintain it, but I'm pretty sure that there won't
be anyone using this ancient hardware and I really doubt the code even
works after the big tty re-arrange.

There is a difference between ancient junk people care about (however
crazy) and stuff that is just dead and slowing real work (and I have
several serial drivers I want to bit bucket such as rio and esp)
--
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/