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
| ||
|
Message-ID: <Pine.LNX.4.64.0702081548450.7686@pentafluge.infradead.org> Date: Thu, 8 Feb 2007 15:51:08 +0000 (GMT) From: James Simmons <jsimmons@...radead.org> To: Greg KH <greg@...ah.com> cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org> Subject: device_destroy While porting over a few class_devices I discovered a problem with device_destroy. It uses a dev_t which several classes don't use. Should all classes require a dev_t or should we just pass in the device itself? - 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/