From: Johannes Berg <johannes@sipsolutions.net>
To: Thomas Pedersen <thomas@cozybit.com>
Cc: linux-wireless@vger.kernel.org, devel@lists.open80211s.org
Subject: Re: [PATCH 6/6] mac80211: init mesh timer for user authed STAs
Date: Tue, 05 Mar 2013 19:59:19 +0100 [thread overview]
Message-ID: <1362509959.638.0.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1362204172-28307-6-git-send-email-thomas@cozybit.com> (sfid-20130302_070418_159027_710EC375)
On Fri, 2013-03-01 at 22:02 -0800, Thomas Pedersen wrote:
> There is a corner case which wasn't being covered:
> userspace may authenticate and allocate stations,
> but still leave the peering up to the kernel.
>
> Initialize the peering timer if the MPM is not in
> userspace, in a path which is taken by both the kernel and
> userspace when allocating stations.
Applied this one.
johannes
next prev parent reply other threads:[~2013-03-05 18:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-02 6:02 [PATCH 1/6] nl80211: explicit userspace MPM Thomas Pedersen
2013-03-02 6:02 ` [PATCH 2/6] cfg80211: rename mesh station types Thomas Pedersen
2013-03-02 6:02 ` [PATCH 3/6] mac80211: support userspace MPM Thomas Pedersen
2013-03-02 6:02 ` [PATCH 4/6] nl80211: user_mpm overrides auto_open_plinks Thomas Pedersen
2013-03-04 15:10 ` Johannes Berg
2013-03-04 20:04 ` Thomas Pedersen
2013-03-04 20:07 ` Johannes Berg
2013-03-02 6:02 ` [PATCH 5/6] mac80211: disallow changing auto_open_plinks Thomas Pedersen
2013-03-02 6:02 ` [PATCH 6/6] mac80211: init mesh timer for user authed STAs Thomas Pedersen
2013-03-04 15:11 ` Johannes Berg
2013-03-04 20:05 ` Thomas Pedersen
2013-03-04 21:10 ` Thomas Pedersen
2013-03-05 18:55 ` Johannes Berg
2013-03-05 18:59 ` Johannes Berg [this message]
2013-03-04 15:09 ` [PATCH 1/6] nl80211: explicit userspace MPM Johannes Berg
2013-03-04 19:59 ` Thomas Pedersen
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=1362509959.638.0.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=devel@lists.open80211s.org \
--cc=linux-wireless@vger.kernel.org \
--cc=thomas@cozybit.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).