From: "Miles Lane" <miles.lane@gmail.com>
To: "Johannes Berg" <johannes@sipsolutions.net>
Cc: "Jiri Benc" <jbenc@suse.cz>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: mac80211 -- My log files are filling up with: "wlan0: RX non-WEP frame, but expected encryption"
Date: Thu, 3 Apr 2008 09:24:16 -0400 [thread overview]
Message-ID: <a44ae5cd0804030624u40be9ad9rb1cadefadb13f889@mail.gmail.com> (raw)
In-Reply-To: <a44ae5cd0804030615n3c3e906ey1db4513802bdf01@mail.gmail.com>
Thanks. I think I have a working build, but can you confirm that the
linker messages are benign?
I will get to work now on getting the log for you.
Now I get:
# make
CC iw.o
cc: -lnl: linker input file unused because linking not done
CC interface.o
interface.c: In function 'handle_interface':
interface.c:64: warning: 'err' may be used uninitialized in this function
interface.c:64: note: 'err' was declared here
interface.c:138: warning: 'err' may be used uninitialized in this function
interface.c:138: note: 'err' was declared here
cc: -lnl: linker input file unused because linking not done
CC info.o
cc: -lnl: linker input file unused because linking not done
CC station.o
cc: -lnl: linker input file unused because linking not done
CC util.o
cc: -lnl: linker input file unused because linking not done
CC mpath.o
cc: -lnl: linker input file unused because linking not done
CC iw
next prev parent reply other threads:[~2008-04-03 13:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a44ae5cd0804021732s6ae5ed81ma5e229ae0faf4aaf@mail.gmail.com>
2008-04-03 12:45 ` mac80211 -- My log files are filling up with: "wlan0: RX non-WEP frame, but expected encryption" Johannes Berg
2008-04-03 13:15 ` Miles Lane
2008-04-03 13:19 ` Johannes Berg
2008-04-03 13:24 ` Miles Lane [this message]
2008-04-03 13:30 ` Johannes Berg
2008-04-03 13:32 ` Miles Lane
2008-04-03 13:34 ` Johannes Berg
2008-04-03 13:36 ` Johannes Berg
2008-04-03 14:01 ` Johannes Berg
2008-04-03 16:52 ` Jouni Malinen
2008-04-03 17:14 ` Miles Lane
2008-04-04 14:51 ` 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=a44ae5cd0804030624u40be9ad9rb1cadefadb13f889@mail.gmail.com \
--to=miles.lane@gmail.com \
--cc=jbenc@suse.cz \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
/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