| 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: <93B2DBD6-0E5F-485F-A785-25328271AF2D@kernel.crashing.org> Date: Tue, 21 Nov 2006 22:38:19 -0600 From: Kumar Gala <galak@...nel.crashing.org> To: Benjamin Herrenschmidt <benh@...nel.crashing.org> Cc: Greg KH <greg@...ah.com>, Linux Kernel list <linux-kernel@...r.kernel.org> Subject: Re: bus_id collisions On Nov 21, 2006, at 12:49 AM, Benjamin Herrenschmidt wrote: > >> Oh, that's a very annoying bus id, but I guess it's legal. >> >> I'll poke around and see if I can make it bigger. You don't want it >> bigger for static 'struct device' types, right? > > Don't bother too much if it's complicated. I'm trying other options as > well, like possibly using the Open Firmware "phandle" (sort of object > ID) which is only 32 bits, provided I can get the embedded folks to > agree to have one at all... Hopefully, we will not complain too much. I can't imagine an extra 32-bits for the two dozen or so nodes we have in a embedded tree is going to cause any heart burn. - k - 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