From: Johannes Berg <johannes@sipsolutions.net>
To: Colleen Twitty <colleen@cozybit.com>
Cc: open80211s <devel@lists.open80211s.org>,
linux-wirelss <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v3 1/2] cfg80211: Userspace may inform kernel of mesh auth method.
Date: Mon, 13 May 2013 11:44:41 +0200 [thread overview]
Message-ID: <1368438281.8300.12.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1368038760-17752-1-git-send-email-colleen@cozybit.com> (sfid-20130508_204609_420695_1F27EE7D)
On Wed, 2013-05-08 at 11:45 -0700, Colleen Twitty wrote:
> Authentication takes place in userspace, but the beacon is
> generated in the kernel. Allow userspace to inform the
> kernel of the authentication method so the appropriate
> mesh config IE can be set prior to beacon generation when
> joining the MBSS.
Applied, thanks.
johannes
prev parent reply other threads:[~2013-05-13 9:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-08 18:45 [PATCH v3 1/2] cfg80211: Userspace may inform kernel of mesh auth method Colleen Twitty
2013-05-08 18:46 ` [PATCH v3 2/2] mac80211: enable Auth Protocol Identifier on mesh config Colleen Twitty
2013-05-13 9:44 ` 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=1368438281.8300.12.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=colleen@cozybit.com \
--cc=devel@lists.open80211s.org \
--cc=linux-wireless@vger.kernel.org \
/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