From: Johannes Berg <johannes@sipsolutions.net>
To: Javier Cardona <javier@cozybit.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
Steve Derosier <steve@cozybit.com>,
devel@lists.open80211s.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 3/3 v2] mac80211: Send mesh non-HWMP path selection frames to userspace
Date: Thu, 16 Dec 2010 19:56:33 +0100 [thread overview]
Message-ID: <1292525793.3612.30.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <1292524200-14791-3-git-send-email-javier@cozybit.com>
On Thu, 2010-12-16 at 10:30 -0800, Javier Cardona wrote:
> Let path selection frames for protocols other than HWMP be sent to
> userspace via NL80211_CMD_REGISTER_FRAME. Also allow userspace to send
> and receive mesh path selection frames.
Looks fine, thanks.
johannes
next prev parent reply other threads:[~2010-12-16 18:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-10 23:04 [PATCH 0/2] mac80211/open80211s: Support alternative path selection algorithms Javier Cardona
2010-12-10 23:04 ` [PATCH 1/2] mac80211: Let userspace enable and configure vendor specific path selection Javier Cardona
2010-12-13 10:04 ` Johannes Berg
2010-12-16 18:29 ` [PATCH 1/3 v2] mac80211: Rename mesh_params to mesh_config to prepare for mesh_setup Javier Cardona
2010-12-16 18:51 ` Johannes Berg
2010-12-17 1:25 ` [PATCH 1/3 v3] " Javier Cardona
2010-12-17 1:37 ` Javier Cardona
2010-12-17 1:37 ` [PATCH 2/3 v3] mac80211: Let userspace enable and configure vendor specific path selection Javier Cardona
2010-12-17 1:37 ` [PATCH 3/3 v3] mac80211: Send mesh non-HWMP path selection frames to userspace Javier Cardona
2010-12-16 18:29 ` [PATCH 2/3 v2] mac80211: Let userspace enable and configure vendor specific path selection Javier Cardona
2010-12-16 18:55 ` Johannes Berg
2010-12-16 18:30 ` [PATCH 3/3 v2] mac80211: Send mesh non-HWMP path selection frames to userspace Javier Cardona
2010-12-16 18:56 ` Johannes Berg [this message]
2010-12-10 23:04 ` [PATCH 2/2] " Javier Cardona
2010-12-13 10:11 ` 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=1292525793.3612.30.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=devel@lists.open80211s.org \
--cc=javier@cozybit.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=steve@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).