From: Johannes Berg <johannes@sipsolutions.net>
To: Vivekananda Holla <vivekanandah@posedge.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [Patch] mac80211: SMPS for AP Mode
Date: Wed, 10 Apr 2013 10:55:51 +0200 [thread overview]
Message-ID: <1365584151.8388.0.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <516528C8.90509@posedge.com> (sfid-20130410_105443_117821_9F07C071)
On Wed, 2013-04-10 at 14:24 +0530, Vivekananda Holla wrote:
> Patch for SMPS mode for AP. This is to define a new ieee80211_tx_info flag to allow a lower AP driver to set RTS/CTS protection for a dynamic SMPS station
>
> Signed-off-by: Vivekananda Holla <vivekanandah@posedge.com>
> ---
> include/net/mac80211.h | 4 ++++
> net/mac80211/rc80211_minstrel_ht.c | 3 +++
> 2 files changed, 7 insertions(+), 0 deletions(-)
>
> diff --git a/include/net/mac80211.h b/include/net/mac80211.h
> index 64faf01..48a950c 100644
> --- a/include/net/mac80211.h
> +++ b/include/net/mac80211.h
> @@ -458,6 +458,9 @@ struct ieee80211_bss_conf {
> * @IEEE80211_TX_CTL_DONTFRAG: Don't fragment this packet even if it
> * would be fragmented by size (this is optional, only used for
> * monitor injection).
> + * @IEEE80211_TX_CTL_SMPS_SET_RTS: set the RTS/CTS protection mechanism
> + * for the packet at AP when SMPS mode at the station is
> + * dynamic SMPS.
Huh? No ... There are perfectly usable flags already inside each rate.
johannes
next prev parent reply other threads:[~2013-04-10 8:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-10 8:54 [Patch] mac80211: SMPS for AP Mode Vivekananda Holla
2013-04-10 8:55 ` Johannes Berg [this message]
2013-04-10 9:35 ` Vivekananda Holla
2013-04-10 9:46 ` Johannes Berg
2013-04-10 9:47 ` Johannes Berg
2013-04-10 9:55 ` Vivekananda Holla
-- strict thread matches above, loose matches on Subject: below --
2013-04-10 10:42 Vivekananda Holla
2013-04-10 11:18 ` Johannes Berg
2013-04-11 5:21 ` vivekanandah
2013-04-11 8:22 ` 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=1365584151.8388.0.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=vivekanandah@posedge.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).