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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <4AD77AC3.7040905@s5r6.in-berlin.de>
Date:	Thu, 15 Oct 2009 21:40:51 +0200
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	david@...g.hm
CC:	Greg KH <gregkh@...e.de>,
	Bartlomiej Zolnierkiewicz <bzolnier@...il.com>,
	Stefan Richter <stefanr@...6.in-berlin.de>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Ingo Molnar <mingo@...e.hu>
Subject: Re: removing existing working drivers via staging

david@...g.hm wrote:
> a driver in staging will be able to build, but a driver that was removed
> after 6-9 months that a user discovered the removal of a year later when
> they upgraded to a new distro release (say a normal ubuntu release after
> staying on the old one for the 18 month support period) is likely to
> need significant work to catch up with kernel changes in the meanwhile.

I don't think this new mechanism is meant to be, or can ever be, a way
to remove things that work and that users need.

Hence the timeline of 3 releases per <20091015164726.GA10125@...e.de>
affects developers/ janitors much more than end users.
-- 
Stefan Richter
-=====-==--= =-=- -====
http://arcgraph.de/sr/
--
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/