From: Arnd Bergmann <arnd@arndb.de>
To: Dwayne Grant McConnell <decimal@us.ibm.com>
Cc: linuxppc-dev@ozlabs.org, cbe-oss-dev@ozlabs.org,
linux-kernel@vger.kernel.org
Subject: Re: Correct way to format spufs file output.
Date: Fri, 20 Oct 2006 16:38:50 +0200 [thread overview]
Message-ID: <200610201638.52404.arnd@arndb.de> (raw)
In-Reply-To: <Pine.WNT.4.64.0610200848580.5976@dwayne>
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 <><
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: Dwayne Grant McConnell <decimal@us.ibm.com>
Cc: cbe-oss-dev@ozlabs.org, linux-kernel@vger.kernel.org,
linuxppc-dev@ozlabs.org
Subject: Re: Correct way to format spufs file output.
Date: Fri, 20 Oct 2006 16:38:50 +0200 [thread overview]
Message-ID: <200610201638.52404.arnd@arndb.de> (raw)
In-Reply-To: <Pine.WNT.4.64.0610200848580.5976@dwayne>
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 <><
next prev parent reply other threads:[~2006-10-20 14:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.WNT.4.64.0610182227120.6056@doodlebug>
2006-10-20 8:23 ` Correct way to format spufs file output Arnd Bergmann
2006-10-20 8:23 ` Arnd Bergmann
2006-10-20 13:54 ` Dwayne Grant McConnell
2006-10-20 13:54 ` Dwayne Grant McConnell
2006-10-20 14:38 ` Arnd Bergmann [this message]
2006-10-20 14:38 ` Arnd Bergmann
2006-10-20 14:42 ` Dwayne Grant McConnell
2006-10-20 14:42 ` Dwayne Grant McConnell
2006-10-21 1:44 ` [Cbe-oss-dev] " Benjamin Herrenschmidt
2006-10-21 1:44 ` Benjamin Herrenschmidt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200610201638.52404.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=cbe-oss-dev@ozlabs.org \
--cc=decimal@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.