From: David Miller <davem@davemloft.net>
To: gang.chen.5i5j@gmail.com
Cc: gerrit@erg.abdn.ac.uk, gxt@mprc.pku.edu.cn, dccp@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH linux-next] net/dccp/timer.c: use 'u64' instead of 's64' to avoid compiler's warning
Date: Thu, 22 May 2014 15:33:13 -0400 (EDT) [thread overview]
Message-ID: <20140522.153313.958087444510569794.davem@davemloft.net> (raw)
In-Reply-To: <537BF116.9000900@gmail.com>
From: Chen Gang <gang.chen.5i5j@gmail.com>
Date: Wed, 21 May 2014 08:19:34 +0800
> 'dccp_timestamp_seed' is initialized once by ktime_get_real() in
> dccp_timestamping_init(). It is always less than ktime_get_real()
> in dccp_timestamp().
>
> Then, ktime_us_delta() in dccp_timestamp() will always return positive
> number. So can use manual type cast to let compiler and do_div() know
> about it to avoid warning.
>
> The related warning (with allmodconfig under unicore32):
>
> CC [M] net/dccp/timer.o
> net/dccp/timer.c: In function ‘dccp_timestamp’:
> net/dccp/timer.c:285: warning: comparison of distinct pointer types lacks a cast
>
>
> Signed-off-by: Chen Gang <gang.chen.5i5j@gmail.com>
Applied to net-next, thanks.
But that type check in include/asm-generic/div64.h is bogus, it should
be checking sizeof(X) == 8 rather than the type thing, it just wants to
make sure that the value is 64-bit regardless of it's signedness.
The arch local implementations do not do this, and that's why very few
other people notice this warning.
next prev parent reply other threads:[~2014-05-22 19:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-21 0:19 [PATCH linux-next] net/dccp/timer.c: use 'u64' instead of 's64' to avoid compiler's warning Chen Gang
2014-05-22 0:26 ` 回复: " 管雪涛
2014-05-22 1:01 ` Chen Gang
2014-05-22 1:06 ` 回复: " 管雪涛
2014-05-22 1:14 ` Chen Gang
2014-05-22 19:33 ` David Miller [this message]
2014-05-22 23:58 ` 回复: " 管雪涛
2014-05-23 1:43 ` Chen Gang
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=20140522.153313.958087444510569794.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dccp@vger.kernel.org \
--cc=gang.chen.5i5j@gmail.com \
--cc=gerrit@erg.abdn.ac.uk \
--cc=gxt@mprc.pku.edu.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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 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).