| 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: Fri, 20 Oct 2006 16:38:50 +0200 From: Arnd Bergmann <arnd@...db.de> To: Dwayne Grant McConnell <decimal@...ibm.com> Cc: cbe-oss-dev@...abs.org, linux-kernel@...r.kernel.org, linuxppc-dev@...abs.org Subject: Re: Correct way to format spufs file output. On Friday 20 October 2006 15:54, Dwayne Grant McConnell wrote: > I think %0xllx is the way to go. I would even advocate changing > signal1_type and signal2_type unless it is actually too dangerous. There is absolutely no reason why these should be hexadecimal, they are basically implementing a bool. > Is there even a case where changing from %llu to %0xllx would break things? > Perhaps with the combination of a old library with a new kernel? Right, a library or some script that has been written assuming there is no leading 0x. Arnd <>< - 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