From: "René Bolldorf" <xsecute@googlemail.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: wireless tree build warnings
Date: Thu, 31 Dec 2009 01:56:49 +0100 [thread overview]
Message-ID: <4B3BF6D1.6010209@googlemail.com> (raw)
In-Reply-To: <20091231105709.c50f22c0.sfr@canb.auug.org.au>
On 12/31/09 00:57, Stephen Rothwell wrote:
> Hi John,
>
> Today's linux-next build (i386 defconfig) produced thes warnings:
>
> net/mac80211/work.c: In function 'ieee80211_remain_on_channel_timeout':
> net/mac80211/work.c:534: warning: cast from pointer to integer of different size
> net/mac80211/work.c: In function 'ieee80211_remain_done':
> net/mac80211/work.c:1030: warning: cast from pointer to integer of different size
> net/mac80211/work.c: In function 'ieee80211_wk_remain_on_channel':
> net/mac80211/work.c:1056: warning: cast from pointer to integer of different size
> net/mac80211/work.c: In function 'ieee80211_wk_cancel_remain_on_channel':
> net/mac80211/work.c:1072: warning: cast from pointer to integer of different size
>
> Introduced by commits e4da8c37af626001ff704fb29ea14eb58f5f7208
> ("mac80211: make off-channel work generic") and
> b8bc4b0aa9bfba755c64b11b8f60e6cfab25dc9d ("mac80211: support
> remain-on-channel command").
>
Hi,
shouldn't it be u32 instead of u64? Please correct me if I'am wrong.
Example:
cfg80211_ready_on_channel(wk->sdata->dev, (u32)wk, wk->chan,
wk->chan_type, wk->remain.duration, GFP_KERNEL);
instead of:
cfg80211_ready_on_channel(wk->sdata->dev, (u64)wk, wk->chan,
wk->chan_type, wk->remain.duration, GFP_KERNEL);
I wish you all a happy new year!
next prev parent reply other threads:[~2009-12-31 0:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-30 23:57 linux-next: wireless tree build warnings Stephen Rothwell
2009-12-31 0:56 ` René Bolldorf [this message]
2009-12-31 2:00 ` Stephen Rothwell
2009-12-31 13:19 ` Johannes Berg
-- strict thread matches above, loose matches on Subject: below --
2009-08-10 9:41 Stephen Rothwell
2009-08-10 17:29 ` Luciano Coelho
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=4B3BF6D1.6010209@googlemail.com \
--to=xsecute@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linville@tuxdriver.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;
as well as URLs for NNTP newsgroup(s).