From: Dave <kilroyd@googlemail.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] mac80211: avoid "Wireless Event too big" message for assoc response
Date: Thu, 02 Oct 2008 22:24:47 +0100 [thread overview]
Message-ID: <48E53C1F.4040909@gmail.com> (raw)
In-Reply-To: <1222890302-32486-1-git-send-email-linville@linville-t61.local>
John W. Linville wrote:
> An attempt was made by Jouni Malinen to correct this issue by
> converting to use IWEVASSOCREQIE and IWEVASSOCRESPIE messages instead
> ("mac80211: Use IWEVASSOCREQIE instead of IWEVCUSTOM"). Unfortunately,
> that caused a problem due to 32-/64-bit interactions on some systems and
> was reverted after the 'userland ABI' rule was invoked.
I was unaware of this, and used IWEVASSOCREQIE and IWEVASSOCRESPIE in the
orinoco wpa updates since the events were available in linux/wireless.h.
Should I post a patch to use IWEVCUSTOM instead?
Thanks,
Dave.
next prev parent reply other threads:[~2008-10-02 21:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-01 19:45 [PATCH] mac80211: avoid "Wireless Event too big" message for assoc response John W. Linville
2008-10-02 21:24 ` Dave [this message]
2008-10-06 17:53 ` John W. Linville
2008-10-06 18:22 ` Jouni Malinen
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=48E53C1F.4040909@gmail.com \
--to=kilroyd@googlemail.com \
--cc=linux-wireless@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).