All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Gabriel C <nix.or.die@googlemail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Gabriel C <crazy@frugalware.org>
Subject: Re: kernel/time.c: integer constant is too large for 'long' type warnings
Date: Fri, 04 Apr 2008 11:06:08 -0700	[thread overview]
Message-ID: <47F66E10.8030405@zytor.com> (raw)
In-Reply-To: <47F65AE6.4050500@googlemail.com>

Gabriel C wrote:
> Hi,
> 
> with CONFIG_HZ_300=y I see these warnings :
> 
> kernel/time.c: In function 'msecs_to_jiffies':                                                                                                               
> kernel/time.c:472: warning: integer constant is too large for 'long' type                                                                                    
> kernel/time.c: In function 'usecs_to_jiffies':                                                                                                               
> kernel/time.c:487: warning: integer constant is too large for 'long' type
> 
> I think this was introduced by :
> 
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=bdc807871d58285737d50dc6163d0feb72cb0dc2
> 
> If you need more infos let me know.
> 

There is a patch for this, already, but the bikeshed painters have been 
whining about it.

The code is correct; it is a nuisance warning only.

	-hpa

      reply	other threads:[~2008-04-04 18:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-04 16:44 kernel/time.c: integer constant is too large for 'long' type warnings Gabriel C
2008-04-04 18:06 ` H. Peter Anvin [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=47F66E10.8030405@zytor.com \
    --to=hpa@zytor.com \
    --cc=crazy@frugalware.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nix.or.die@googlemail.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 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.