From: Bob Copeland <me@bobcopeland.com>
To: devel@lists.open80211s.org
Cc: johannes@sipsolutions.net, Mike Krinkin <krinkin.m.u@gmail.com>,
Ivan Bezyazychnyy <ivan.bezyazychnyy@gmail.com>,
linux-wireless@vger.kernel.org, Max Filippov <jcmvbkbc@gmail.com>
Subject: Re: [RFCv3 4/5] mac80211: mesh power save basics
Date: Fri, 7 Dec 2012 17:41:10 -0500 [thread overview]
Message-ID: <20121207224110.GE535@localhost> (raw)
In-Reply-To: <1354918443-3076-5-git-send-email-marco@cozybit.com>
On Fri, Dec 07, 2012 at 02:14:02PM -0800, Marco Porsch wrote:
> +void ieee80211_mps_set_sta_local_pm(struct sta_info *sta,
> + enum nl80211_mesh_power_mode pm,
> + u32 delay);
> +void ieee80211_mps_sta_local_pm_timer(unsigned long data);
> +void ieee80211_msp_set_frame_flags(struct ieee80211_sub_if_data *sdata,
> + struct sta_info *sta,
> + struct ieee80211_hdr *hdr);
Does "msp" mean anything, or is it supposed to be mps like the others?
--
Bob Copeland %% www.bobcopeland.com
next prev parent reply other threads:[~2012-12-07 22:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-07 22:13 [RFCv3 0/5] mesh power save - basics Marco Porsch
2012-12-07 22:13 ` [RFCv3 1/5] {nl,cfg,mac}80211: set beacon interval and DTIM period on mesh join Marco Porsch
2012-12-07 22:33 ` [RFCv3 1/5] {nl, cfg, mac}80211: " Bob Copeland
2012-12-07 22:14 ` [RFCv3 2/5] cfg80211: mesh power mode primitives Marco Porsch
2012-12-07 22:14 ` [RFCv3 3/5] mac80211: move add_tim to subfunction Marco Porsch
2012-12-07 22:14 ` [RFCv3 4/5] mac80211: mesh power save basics Marco Porsch
2012-12-07 22:41 ` Bob Copeland [this message]
2012-12-07 22:45 ` Marco Porsch
2012-12-07 22:14 ` [RFCv3 5/5] nl80211: allow userspace to access mesh power mode parameters Marco Porsch
2012-12-11 19:52 ` Johannes Berg
2012-12-11 19:53 ` [RFCv3 0/5] mesh power save - basics 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=20121207224110.GE535@localhost \
--to=me@bobcopeland.com \
--cc=devel@lists.open80211s.org \
--cc=ivan.bezyazychnyy@gmail.com \
--cc=jcmvbkbc@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=krinkin.m.u@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.