| 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, 9 Jun 2011 15:24:27 -0500 From: Timur Tabi <timur@...escale.com> To: Arnd Bergmann <arnd@...db.de> CC: <linux-kernel@...r.kernel.org>, <linuxppc-dev@...ts.ozlabs.org>, <alan@...rguk.ukuu.org.uk>, <kumar.gala@...escale.com>, <benh@...nel.crashing.org>, <greg@...ah.com>, <akpm@...nel.org>, <cmetcalf@...era.com>, <konrad.wilk@...cle.com>, <linux-console@...r.kernel.org> Subject: Re: [PATCH 7/7] [v4] drivers/virt: introduce Freescale hypervisor management driver Arnd Bergmann wrote: > The lesson to learn here is obviously not to ship binaries of applications > to customers before the driver has been merged in a mainline kernel. Believe me, I know this, but unfortunately I have no control over every aspect of our development cycle. > The best way out that I can see is to make the driver carry the proper > interface in the upstream version, but to have a private patch to support > both interface versions in the kernel you ship on machines that require > backwards compatibility. Once you have phased out the user application, > you can then drop that patch and use the upstream version of the > interfaces. I think I can make that work. -- Timur Tabi Linux kernel developer at Freescale -- 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