| 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, 31 Jan 2007 18:00:15 -0500 From: Theodore Tso <tytso@....edu> To: Greg KH <greg@...ah.com> Cc: Nicolas Mailhot <nicolas.mailhot@...oste.net>, linux-kernel@...r.kernel.org Subject: Re: Free Linux Driver Development! On Wed, Jan 31, 2007 at 12:12:58PM -0800, Greg KH wrote: > > This kind of offer has _always_ been there for out-of-tree GPL drivers. > I have contacted many different groups and driver authors over the years > to offer my help in trying to get their code into the mainline kernel. > > Some take me up on the offer, others ignore it, and still others activly > refuse to do so, saying they want to stay out-of-the tree (lirc is one > of these examples...) I think the point is that if we are offering free development effort to write a driver which goes into mainline, maybe we should provide more than "providing rules and guidelines" so that people can spend engineering $$$ to get the driver into mainline. More specifically, Dave said that it "seemed rude" to just take the driver and send updates, but maybe the best way of dealing with out-of-tree drivers like lirc is to treat the out-of-tree drivers as a kind of spec release, and just have someone in the community forcibly take the code, fix it up, and then get it merged. Maybe it's being "rude", but so is not responding to requests to get it merged. - Ted - 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