| 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
| ||
|
Date: Wed, 28 Nov 2007 14:04:09 -0500 From: lsorense@...lub.uwaterloo.ca (Lennart Sorensen) To: Jon Smirl <jonsmirl@...il.com> Cc: Jean Delvare <khali@...ux-fr.org>, Russell King <rmk+kernel@....linux.org.uk>, Adrian Bunk <bunk@...nel.org>, i2c@...sensors.org, Lennert Buytenhek <buytenh@...tstofly.org>, linux-kernel@...r.kernel.org Subject: Re: [i2c] [2.6 patch] some overdue I2C driver removal On Wed, Nov 28, 2007 at 12:43:00PM -0500, Jon Smirl wrote: > Hasn't their been a one year notice that these drivers were going to > be removed? How about removing them and putting them into a tarball on > the i2c web site with a note explaining about how they need to be > updated to use the gpio driver? Then if someone really wants to use > the old drivers they can use them out of tree. Why remove a working driver? Who gets to decide that everyone must go use this gpio api based system that isn't yet supported by all platforms? If someone thinks the old drivers should be replaced by new ones using the new GPIO API then they should go implement it, and then when it works they can remove the old one. You can't just declare that you think the old one sucks and should be removed and if anyone else cares they should go make a working driver to replace it. -- Len Sorensen - 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/
Powered by blists - more mailing lists