From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Tim Deegan <Tim.Deegan@citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] timer.c: Cast time value so that it has the correct type
Date: Thu, 19 Aug 2010 15:46:44 +0100 [thread overview]
Message-ID: <C8930264.1E827%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <20100819143704.GI20252@whitby.uk.xensource.com>
This is my mistake, I'll do a patch to use the appropriate PRI macro.
-- Keir
On 19/08/2010 15:37, "Tim Deegan" <Tim.Deegan@citrix.com> wrote:
> At 15:13 +0100 on 19 Aug (1282230825), Ian Jackson wrote:
>> We'd prefer to avoid PRI macros in xen itself
>
> I don't think we would; we even define a bunch of our own. :)
>
>> , so instead we cast the
>> value to long to match the printf format. Without this, the build
>> fails on some compilers.
>
> This is the wrong fix; on PAE builds the value will be truncated from 64
> bits to 32.
>
> Cheers,
>
> Tim.
>
>> Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com>
>>
>> diff -r a05a2d559931 xen/common/timer.c
>> --- a/xen/common/timer.c Thu Aug 19 14:46:32 2010 +0100
>> +++ b/xen/common/timer.c Thu Aug 19 15:12:36 2010 +0100
>> @@ -500,7 +500,7 @@ static void dump_timer(struct timer *t,
>> static void dump_timer(struct timer *t, s_time_t now)
>> {
>> printk(" ex=%8ldus timer=%p cb=%p(%p)",
>> - (t->expires - now) / 1000, t, t->function, t->data);
>> + (long)((t->expires - now) / 1000), t, t->function, t->data);
>> print_symbol(" %s\n", (unsigned long)t->function);
>> }
>>
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
prev parent reply other threads:[~2010-08-19 14:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-19 14:13 [PATCH] timer.c: Cast time value so that it has the correct type Ian Jackson
2010-08-19 14:37 ` Tim Deegan
2010-08-19 14:46 ` Keir Fraser [this message]
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=C8930264.1E827%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=Tim.Deegan@citrix.com \
--cc=xen-devel@lists.xensource.com \
/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;
as well as URLs for NNTP newsgroup(s).