linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Will Hawkins <hawkinsw@opentechinstitute.org>
To: linux-wireless@vger.kernel.org,
	Johannes Berg <johannes@sipsolutions.net>,
	linville@tuxdriver.com
Subject: [PATCH 0/2 v3] mac80211/cfg80211: add support for userspace to handle auth frames on adhoc ifaces
Date: Mon, 18 Jun 2012 20:19:58 -0400	[thread overview]
Message-ID: <4FDFC5AE.1080004@opentechinstitute.org> (raw)

Hello!

I am sending along 2 patches to add support for user space applications
to register for authentication frames on adhoc interfaces. These are
revisions to a previous patch that I submitted to accomplish the same
thing.

Patch 1/2 adds a cfg80211_mgmt_reg_match function to cfg80211 to
check whether a user space application is registered for a particular
type of management frame rx'd on a particular device. The new function
is very similar to cfg80211_rx_mgmt. cfg80211_rx_mgmt could not be
reused because of its side-effect of transmitting the "query" frames to
the registered userspace applications. This patch modifies the
documentation for cfg80211_rx_mgmt to reflect that.

Patch 2/2 sets the necessary flags to allow userspace
applications to register for authentication frames on adhoc interfaces.
It also adds a check to make sure that "open" authentication frames are
not sent when a user space application is registered for authentication
frames.

As I've said before, I'm still new to this process so I look forward to
your feedback on improving.

Will

             reply	other threads:[~2012-06-19  0:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-19  0:19 Will Hawkins [this message]
2012-06-19  7:05 ` [PATCH 0/2 v3] mac80211/cfg80211: add support for userspace to handle auth frames on adhoc ifaces 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=4FDFC5AE.1080004@opentechinstitute.org \
    --to=hawkinsw@opentechinstitute.org \
    --cc=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).