linux-kernel - Re: Correct way to format spufs file output.

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.WNT.4.64.0610200941530.5976@dwayne>
Date:	Fri, 20 Oct 2006 09:42:21 -0500 (Central Daylight Time)
From:	Dwayne Grant McConnell <decimal@...ibm.com>
To:	Arnd Bergmann <arnd@...db.de>
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 Fri, 20 Oct 2006, Arnd Bergmann wrote:

> 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.

Okay. Thanks for considering it. I'll leave the %llu as is.

-- 
Dwayne Grant McConnell <decimal@...ibm.com>
Lotus Notes Mail: Dwayne McConnell [Mail]/Austin/IBM@...US
Lotus Notes Calendar: Dwayne McConnell [Calendar]/Austin/IBM@...US

-
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/