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, 18 Jan 2007 09:45:04 +0530 From: "Daniel Rodrick" <daniel.rodrick@...il.com> To: kernelnewbies <kernelnewbies@...linux.org>, "Linux Newbie" <linux-newbie@...r.kernel.org>, linux-kernel@...r.kernel.org Subject: after effects of a kernel API change Hi list, Whenever there is a change in the kernel API (or a new API is introduced), all of the drivers that use the older API need to be changed (or recommended to be changed). I believe it is the responsibility of the person changing the kernel API, to change all the drivers that have found their way into the kernel code? How does this happen? Because the person who brought the change in the API might not know the internals of all the drivers? Is there any way volunteers like me can help in this exercise? Thanks, Dan - 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