From: Johannes Berg <johannes@sipsolutions.net>
To: Thomas Pedersen <thomas@cozybit.com>
Cc: linux-wireless@vger.kernel.org, devel@lists.open80211s.org,
Javier Cardona <javier@cozybit.com>
Subject: Re: [PATCH 7/7] mac80211: Check auth status before attempting to establish a peer link
Date: Fri, 04 Mar 2011 12:37:35 +0100 [thread overview]
Message-ID: <1299238655.4348.7.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <1299208307-9428-8-git-send-email-thomas@cozybit.com>
On Thu, 2011-03-03 at 19:11 -0800, Thomas Pedersen wrote:
> From: Javier Cardona <javier@cozybit.com>
And this patch would also not be necessary since there wouldn't be a
station entry to start with.
johannes
prev parent reply other threads:[~2011-03-04 11:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-04 3:11 Thomas Pedersen
2011-03-04 3:11 ` [PATCH 1/7] mac80211: Support RSN information element on mesh interfaces Thomas Pedersen
2011-03-04 11:30 ` Johannes Berg
2011-03-04 18:48 ` Javier Cardona
2011-03-04 3:11 ` [PATCH 2/7] mac80211: New constant definitions for SAE Thomas Pedersen
2011-03-04 11:32 ` Johannes Berg
2011-03-04 18:51 ` Javier Cardona
2011-03-04 3:11 ` [PATCH 3/7] mac80211: Let user space receive and send mesh auth/deauth frames Thomas Pedersen
2011-03-04 3:11 ` [PATCH 4/7] mac80211: Accept mesh auth frames before a peer link has been established Thomas Pedersen
2011-03-04 3:11 ` [PATCH 5/7] nl80211: Let userspace set the authenticated flag for a mesh peer Thomas Pedersen
2011-03-04 11:36 ` Johannes Berg
2011-03-04 19:01 ` Javier Cardona
2011-03-04 19:14 ` Johannes Berg
2011-03-04 3:11 ` [PATCH 6/7] mac80211: Parse RSN information element to determine if a peer needs authentication Thomas Pedersen
2011-03-04 11:37 ` Johannes Berg
2011-03-04 19:06 ` Javier Cardona
2011-03-04 19:18 ` Johannes Berg
2011-03-04 19:45 ` Javier Cardona
2011-03-04 19:52 ` Johannes Berg
2011-03-04 3:11 ` [PATCH 7/7] mac80211: Check auth status before attempting to establish a peer link Thomas Pedersen
2011-03-04 11:37 ` Johannes Berg [this message]
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=1299238655.4348.7.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=devel@lists.open80211s.org \
--cc=javier@cozybit.com \
--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).