From: Anthony Liguori <anthony@codemonkey.ws>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v2] qtest: avoid a warning with RTC test
Date: Fri, 30 Mar 2012 14:21:58 -0500 [thread overview]
Message-ID: <4F7607D6.40003@codemonkey.ws> (raw)
In-Reply-To: <CAAu8pHuBdTAMSzd=7sH=dVWJVyUwLjBVunaPuHTntJUkvhdysA@mail.gmail.com>
On 03/30/2012 02:19 PM, Blue Swirl wrote:
> Avoid this warning on OpenBSD:
> CC tests/rtc-test.o
> /src/qemu/tests/rtc-test.c: In function 'check_time':
> /src/qemu/tests/rtc-test.c:171: warning: format '%ld' expects type
> 'long int', but argument 2 has type 'time_t'
> /src/qemu/tests/rtc-test.c:173: warning: format '%ld' expects type
> 'long int', but argument 2 has type 'time_t'
>
> Signed-off-by: Blue Swirl<blauwirbel@gmail.com>
Reviewed-by: Anthony Liguori <aliguori@us.ibm.com>
Regards,
Anthony Liguori
> ---
>
> v2: make t and s longs.
>
> ---
> tests/rtc-test.c | 6 +++---
> 1 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/tests/rtc-test.c b/tests/rtc-test.c
> index c32b36a..983a980 100644
> --- a/tests/rtc-test.c
> +++ b/tests/rtc-test.c
> @@ -161,12 +161,12 @@ static void check_time(int wiggle)
> }
>
> if (!(tm_cmp(&start, datep)<= 0&& tm_cmp(datep,&end)<= 0)) {
> - time_t t, s;
> + long t, s;
>
> start.tm_isdst = datep->tm_isdst;
>
> - t = mktime(datep);
> - s = mktime(&start);
> + t = (long)mktime(datep);
> + s = (long)mktime(&start);
> if (t< s) {
> g_test_message("RTC is %ld second(s) behind
> wall-clock\n", (s - t));
> } else {
next prev parent reply other threads:[~2012-03-30 19:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-30 19:19 [Qemu-devel] [PATCH v2] qtest: avoid a warning with RTC test Blue Swirl
2012-03-30 19:21 ` Anthony Liguori [this message]
2012-03-30 20:07 ` Blue Swirl
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=4F7607D6.40003@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=aliguori@us.ibm.com \
--cc=blauwirbel@gmail.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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.