| 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: Thu, 28 Jun 2007 09:39:15 -0700 From: William D Waddington <william.waddington@...zmo.com> To: Alan Cox <alan@...rguk.ukuu.org.uk> CC: Helge Hafting <helge.hafting@...el.hist.no>, linux-kernel@...r.kernel.org, Al Boldi <a1426z@...ab.com> Subject: Re: Please release a stable kernel Linux 3.0 Alan Cox wrote: [snip] >> A cleaned-up, consistent, and out-of-tree friendly way of handling API >> changes might help us all. > > The problem is that its very impractical. If I change a kernel API I fix > up the in tree users and test those I can, that's "accepted practice" - > you make mess doing a job you clean it up. I can't do that for out of > tree code because its out of tree. Thanks for the thoughtful reply. _And_ for taking the time to look at the code. I guess my half-assed notion is to have a single file w/"#ifdef-able" entries that flag API changes. It at least would give me/us a single point of reference, and avoid the rather ugly version checking. "LDDx" is fine, and lwn.net has saved my ass more times than I can count, but a single peg on which to hang my out-of-tree hat would seem useful. Thanks again, Bill -- -------------------------------------------- William D Waddington Bainbridge Island, WA, USA william.waddington@...zmo.com -------------------------------------------- "Even bugs...are unexpected signposts on the long road of creativity..." - Ken Burtch - 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