From: Johannes Berg <johannes@sipsolutions.net>
To: John Linville <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org
Subject: [PATCH 0/5] station management rework
Date: Wed, 14 Dec 2011 12:20:26 +0100 [thread overview]
Message-ID: <20111214112026.409514167@sipsolutions.net> (raw)
Thomas was kind enough to look at the previous
patchset for mesh station handling, and I think
this new patchset addresses his concerns.
Arik also helped me look at TDLS, which should
be handled correctly now.
johannes
next reply other threads:[~2011-12-14 11:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-14 11:20 Johannes Berg [this message]
2011-12-14 11:20 ` [PATCH 1/5] cfg80211: validate nl80211 station handling better Johannes Berg
2011-12-14 11:20 ` [PATCH 2/5] mac80211: remove duplicate TDLS peer verification Johannes Berg
2011-12-14 11:20 ` [PATCH 3/5] mac80211: use station mutex in configuration Johannes Berg
2011-12-14 11:20 ` [PATCH 4/5] mac80211: refactor station state transitions Johannes Berg
2011-12-14 11:35 ` [PATCH 4/5 v2] " Johannes Berg
2011-12-14 11:20 ` [PATCH 5/5] mac80211: count authorized stations per BSS Johannes Berg
2011-12-14 11:29 ` [PATCH 0/5] station management rework Johannes Berg
2011-12-14 11:35 ` 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=20111214112026.409514167@sipsolutions.net \
--to=johannes@sipsolutions.net \
--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).