From: Thomas Gleixner <tglx@linutronix.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: caglar@pardus.org.tr,
Venki Pallipadi <venkatesh.pallipadi@intel.com>,
linux-kernel@vger.kernel.org, john stultz <johnstul@us.ibm.com>
Subject: Re: [PATCH] drivers/char/hpet.c: integer constant is too large for "long" type
Date: Tue, 24 Jul 2007 00:08:55 +0200 [thread overview]
Message-ID: <1185228535.3318.44.camel@chaos> (raw)
In-Reply-To: <20070723145940.a99b0324.akpm@linux-foundation.org>
On Mon, 2007-07-23 at 14:59 -0700, Andrew Morton wrote:
> On Sat, 21 Jul 2007 14:19:44 +0300
> "S.__a__lar Onur" <caglar@pardus.org.tr> wrote:
>
> > Following trivial patch silents
> >
> > drivers/char/hpet.c:76: warning: integer constant is too large for "long" type
> >
> > warning (with gcc-3.4.6)
> >
> > Signed-off-by: S.__a__lar Onur <caglar@pardus.org.tr>
> >
> > drivers/char/hpet.c | 2 +-
> > 1 files changed, 1 insertions(+), 1 deletions(-)
> >
> > diff --git a/drivers/char/hpet.c b/drivers/char/hpet.c
> > index ba0e74a..23fadf5 100644
> > --- a/drivers/char/hpet.c
> > +++ b/drivers/char/hpet.c
> > @@ -73,7 +73,7 @@ static struct clocksource clocksource_hpet = {
> > .name = "hpet",
> > .rating = 250,
> > .read = read_hpet,
> > - .mask = 0xffffffffffffffff,
> > + .mask = 0xffffffffffffffffLL,
> > .mult = 0, /*to be caluclated*/
> > .shift = 10,
> > .flags = CLOCK_SOURCE_IS_CONTINUOUS,
>
> hm, well, this does assume that cycle_t is implemented as long long (or
> unsigned long long, actually). Which in turn assumes that u64 is
> implemented as [unsigned] long long.
>
> Not all architectures use unsigned long long for u64: some use unsigned
> long. They'll probably be OK with this change but I think I'll convert
> that into plain old "-1", which just works everywhere.
.mask = CLOCKSOURCE_MASK(64)
should work
tglx
prev parent reply other threads:[~2007-07-23 22:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-21 11:19 S.Çağlar Onur
2007-07-23 21:59 ` Andrew Morton
2007-07-23 22:03 ` Gabriel C
2007-07-23 22:08 ` Thomas Gleixner [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=1185228535.3318.44.camel@chaos \
--to=tglx@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=caglar@pardus.org.tr \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=venkatesh.pallipadi@intel.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
Powered by JetHome