From: Michael Buesch <mb@bu3sch.de>
To: "Tomas Winkler" <tomasw@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: iwl: large integer implicitly truncated to unsigned
Date: Wed, 1 Aug 2007 00:16:19 +0200 [thread overview]
Message-ID: <200708010016.19365.mb@bu3sch.de> (raw)
In-Reply-To: <1ba2fa240707311511y620b205p21cc1b3963e0ef77@mail.gmail.com>
On Wednesday 01 August 2007 00:11:32 Tomas Winkler wrote:
> On 8/1/07, Michael Buesch <mb@bu3sch.de> wrote:
> > Are you aware of these warnings in current wireless-dev?
> >
> > drivers/net/wireless/iwl-base.c:2061: warning: large integer implicitly truncated to unsigned type
> > drivers/net/wireless/iwl-base.c:2062: warning: large integer implicitly truncated to unsigned type
> > drivers/net/wireless/iwl-base.c:2063: warning: large integer implicitly truncated to unsigned type
> > drivers/net/wireless/iwl-base.c:2064: warning: large integer implicitly truncated to unsigned type
> > drivers/net/wireless/iwl-base.c:2065: warning: large integer implicitly truncated to unsigned type
> > drivers/net/wireless/iwl-base.c:2071: warning: large integer implicitly truncated to unsigned type
> > drivers/net/wireless/iwl-base.c:2072: warning: large integer implicitly truncated to unsigned type
> > drivers/net/wireless/iwl-base.c:2073: warning: large integer implicitly truncated to unsigned type
> > drivers/net/wireless/iwl-base.c:2074: warning: large integer implicitly truncated to unsigned type
> > drivers/net/wireless/iwl-base.c:2075: warning: large integer implicitly truncated to unsigned type
> >
> Haven't seen this one. What machine are you running compilation? 64bit maybe?
32bit PPC with gcc 4.1.2
--
Greetings Michael.
next prev parent reply other threads:[~2007-07-31 22:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-31 21:54 iwl: large integer implicitly truncated to unsigned Michael Buesch
2007-07-31 22:11 ` Tomas Winkler
2007-07-31 22:16 ` Michael Buesch [this message]
2007-07-31 22:20 ` Tomas Winkler
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=200708010016.19365.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=linux-wireless@vger.kernel.org \
--cc=tomasw@gmail.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