From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: Andreas Schwab <schwab@suse.de>
Cc: Maxim Uvarov <muvarov@ru.mvista.com>,
LKML <linux-kernel@vger.kernel.org>,
balbir@in.ibm.com, jlan@engr.sgi.com
Subject: Re: [PATCH] Since we have counters in __u64 format we have to print them with %llu macros.
Date: Wed, 26 Sep 2007 17:18:06 +0530 [thread overview]
Message-ID: <46FA46F6.6000707@linux.vnet.ibm.com> (raw)
In-Reply-To: <je641x64rw.fsf@sykes.suse.de>
Andreas Schwab wrote:
> Maxim Uvarov <muvarov@ru.mvista.com> writes:
>
>> diff --git a/Documentation/accounting/getdelays.c b/Documentation/accounting/getdelays.c
>> index cbee3a2..73924df 100644
>> --- a/Documentation/accounting/getdelays.c
>> +++ b/Documentation/accounting/getdelays.c
>> @@ -208,7 +208,7 @@ void print_delayacct(struct taskstats *t)
>> void task_context_switch_counts(struct taskstats *t)
>> {
>> printf("\n\nTask %15s%15s\n"
>> - " %15lu%15lu\n",
>> + " %15llu%15llu\n",
>> "voluntary", "nonvoluntary",
>> t->nvcsw, t->nivcsw);
>
> __u64 is not always long long.
What is the maximum size of long long across all architectures?
How does one format __u64 for printing?
--
Warm Regards,
Balbir Singh
Linux Technology Center
IBM, ISTL
next prev parent reply other threads:[~2007-09-26 11:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-26 14:39 [PATCH] Since we have counters in __u64 format we have to print them with %llu macros Maxim Uvarov
2007-09-26 11:01 ` [PATCH] Since we have counters in __u64 format we have to print themwith " Balbir Singh
2007-09-26 11:32 ` [PATCH] Since we have counters in __u64 format we have to print them with " Andreas Schwab
2007-09-26 11:48 ` Balbir Singh [this message]
2007-09-26 18:22 ` H. Peter Anvin
2007-09-27 8:19 ` Balbir Singh
-- strict thread matches above, loose matches on Subject: below --
2007-09-26 17:52 Maxim Uvarov
2007-09-26 12:36 Mikael Pettersson
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=46FA46F6.6000707@linux.vnet.ibm.com \
--to=balbir@linux.vnet.ibm.com \
--cc=balbir@in.ibm.com \
--cc=jlan@engr.sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=muvarov@ru.mvista.com \
--cc=schwab@suse.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox