All of lore.kernel.org
 help / color / mirror / Atom feed
From: 管雪涛 <gxt@pku.edu.cn>
To: dccp@vger.kernel.org
Subject: 回复: Re: [PATCH linux-next] net/dccp/timer.c: use 
Date: Thu, 22 May 2014 23:58:11 +0000	[thread overview]
Message-ID: <263613432.57393.1400803091663.JavaMail.root@bj-mail03.pku.edu.cn> (raw)
In-Reply-To: <579164883.46799.1400720806850.JavaMail.root@bj-mail03.pku.edu.cn>


----- David Miller <davem@davemloft.net> 写道:
> 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.

Arch-dependent codes implement it with unsigned long long type.
And, every warning should not be ignored.

WARNING: multiple messages have this Message-ID (diff)
From: 管雪涛 <gxt@pku.edu.cn>
To: David Miller <davem@davemloft.net>
Cc: gang chen 5i5j <gang.chen.5i5j@gmail.com>,
	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: Fri, 23 May 2014 07:58:11 +0800 (CST)	[thread overview]
Message-ID: <263613432.57393.1400803091663.JavaMail.root@bj-mail03.pku.edu.cn> (raw)
In-Reply-To: <20140522.153313.958087444510569794.davem@davemloft.net>


----- David Miller <davem@davemloft.net> 写道:
> 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.

Arch-dependent codes implement it with unsigned long long type.
And, every warning should not be ignored.

  reply	other threads:[~2014-05-22 23:58 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-22  1:06 回复: Re: 回复: [PATCH linux- = 管雪涛
2014-05-22  1:06 ` 回复: Re: 回复: [PATCH linux-next] net/dccp/timer.c: use 'u64' instead of 's64' to avoid compiler's warning 管雪涛
2014-05-22 23:58 ` 管雪涛 [this message]
2014-05-22 23:58   ` 回复: " 管雪涛
  -- strict thread matches above, loose matches on Subject: below --
2014-05-23  1:43 回复: Re: [PATCH linux-next] net/d =?UTF-8?B?Y2NwL3RpbWVyLmM6IHVzZ Chen Gang
2014-05-23  1:43 ` 回复: Re: [PATCH linux-next] net/dccp/timer.c: use 'u64' instead of 's64' to avoid compiler's warning Chen Gang
2014-05-22  1:14 回复: Re: 回复: [PATCH linux-n =?UTF-8?B?ZXh0XSBuZXQvZGNjcC90a Chen Gang
2014-05-22  1:14 ` 回复: Re: 回复: [PATCH linux-next] net/dccp/timer.c: use 'u64' instead of 's64' to avoid compiler's warning Chen Gang
2014-05-22  1:01 回复: [PATCH linux-next] net/dccp/ =?UTF-8?B?dGltZXIuYzogdXNlICd1N Chen Gang
2014-05-22  1:01 ` 回复: [PATCH linux-next] net/dccp/timer.c: use 'u64' instead of 's64' to avoid compiler's warning Chen Gang
2014-05-22  0:26 回复: [PATCH linux-next] net/dccp/timer.c: use 'u 管雪涛
2014-05-22  0:26 ` 回复: [PATCH linux-next] net/dccp/timer.c: use 'u64' instead of 's64' to avoid compiler's warning 管雪涛
2014-05-21  0:19 Chen Gang
2014-05-21  0:19 ` Chen Gang
2014-05-22 19:33 ` David Miller
2014-05-22 19:33   ` David Miller
2014-05-22 19:33   ` David Miller

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=263613432.57393.1400803091663.JavaMail.root@bj-mail03.pku.edu.cn \
    --to=gxt@pku.edu.cn \
    --cc=dccp@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 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.