From: Johannes Berg <johannes@sipsolutions.net>
To: Rui Paulo <rpaulo@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: mesh endian bugs
Date: Thu, 19 Nov 2009 23:29:34 +0100 [thread overview]
Message-ID: <1258669774.7094.27.camel@johannes.local> (raw)
In-Reply-To: <7CA4D235-AFC1-4B4A-9025-3A426997706C@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1161 bytes --]
On Thu, 2009-11-19 at 15:50 +0000, Rui Paulo wrote:
> Hi,
>
> On 19 Nov 2009, at 13:51, Johannes Berg wrote:
>
> > CHECK /home/johannes/sys/wireless-testing/net/mac80211/mesh_pathtbl.c
> > /home/johannes/sys/wireless-testing/net/mac80211/mesh_pathtbl.c:471:41: warning: incorrect type in argument 4 (different base types)
> > /home/johannes/sys/wireless-testing/net/mac80211/mesh_pathtbl.c:471:41: expected restricted __le16 [usertype] target_rcode
> > /home/johannes/sys/wireless-testing/net/mac80211/mesh_pathtbl.c:471:41: got int
> > /home/johannes/sys/wireless-testing/net/mac80211/mesh_pathtbl.c:617:36: warning: incorrect type in argument 4 (different base types)
> > /home/johannes/sys/wireless-testing/net/mac80211/mesh_pathtbl.c:617:36: expected restricted __le16 [usertype] target_rcode
> > /home/johannes/sys/wireless-testing/net/mac80211/mesh_pathtbl.c:617:36: got int
>
> Thanks Johannes. How does one perform this check?
make M=net/mac80211 C=1
However, due to a stupid kmemcheck thing it's broken, runs into an error
in skbuff.h and you need to fix that first by removing the :16 on that
line.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2009-11-19 22:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-19 13:51 mesh endian bugs Johannes Berg
2009-11-19 15:50 ` Rui Paulo
2009-11-19 17:20 ` Dan Williams
2009-11-19 22:29 ` Johannes Berg [this message]
2009-11-19 22:30 ` Johannes Berg
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=1258669774.7094.27.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=rpaulo@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