From: Johannes Berg <johannes@sipsolutions.net>
To: Thadeu Lima de Souza Cascardo <cascardo@holoscopio.com>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
Simon Raffeiner <sturmflut@lieberbiber.de>,
Andrey Yurovsky <andrey@cozybit.com>,
Javier Cardona <javier@cozybit.com>
Subject: Re: [PATCH] nl80211: does not allow NEW_STATION and DEL_STATION for mesh
Date: Fri, 12 Feb 2010 15:03:24 +0100 [thread overview]
Message-ID: <1265983404.18938.0.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <20100212135535.GA1123@holoscopio.com>
[-- Attachment #1: Type: text/plain, Size: 758 bytes --]
On Fri, 2010-02-12 at 11:55 -0200, Thadeu Lima de Souza Cascardo wrote:
> Sorry. This code has obviously given me an oops. I did it in a hurry
> and
> thought that was a good optimization to get out as early as possible
> in
> the case the device was not in AP mode.
Which device, at that point :)
> I have fixed it, but I would like to do a more thorough test now to
> make
> up for my mistake.
>
> So, is there any test tool around? I am playing with iw code to do
> these tests. Any recommendations for the values of listen interval and
> the acceptable values for supported rates and aid?
I guess just using hostapd and connecting to it once would be a good
test for that code path, but the rest _looked_ fine to me.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2010-02-12 14:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-12 12:37 [PATCH] nl80211: does not allow NEW_STATION and DEL_STATION for mesh Thadeu Lima de Souza Cascardo
2010-02-12 12:49 ` Johannes Berg
2010-02-12 13:55 ` Thadeu Lima de Souza Cascardo
2010-02-12 14:03 ` Johannes Berg [this message]
2010-02-12 14:34 ` [PATCH v2] " Thadeu Lima de Souza Cascardo
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=1265983404.18938.0.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=andrey@cozybit.com \
--cc=cascardo@holoscopio.com \
--cc=javier@cozybit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=sturmflut@lieberbiber.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.