From: Johannes Berg <johannes@sipsolutions.net>
To: John Linville <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org, Johannes Berg <johannes.berg@intel.com>
Subject: [PATCH 1/4] mac80211: add missing docs for off-chan TX flag
Date: Thu, 06 Jan 2011 22:36:44 +0100 [thread overview]
Message-ID: <20110106213714.894284080@sipsolutions.net> (raw)
In-Reply-To: 20110106213643.454994320@sipsolutions.net
From: Johannes Berg <johannes.berg@intel.com>
The flag is IEEE80211_TX_CTL_TX_OFFCHAN and I had
added that in a previous patch but forgotten docs.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
---
include/net/mac80211.h | 4 ++++
1 file changed, 4 insertions(+)
--- wireless-testing.orig/include/net/mac80211.h 2011-01-06 22:18:55.000000000 +0100
+++ wireless-testing/include/net/mac80211.h 2011-01-06 22:19:53.000000000 +0100
@@ -337,6 +337,10 @@ struct ieee80211_bss_conf {
* @IEEE80211_TX_CTL_LDPC: tells the driver to use LDPC for this frame
* @IEEE80211_TX_CTL_STBC: Enables Space-Time Block Coding (STBC) for this
* frame and selects the maximum number of streams that it can use.
+ * @IEEE80211_TX_CTL_TX_OFFCHAN: Marks this packet to be transmitted on
+ * the off-channel channel when a remain-on-channel offload is done
+ * in hardware -- normal packets still flow and are expected to be
+ * handled properly by the device.
*
* Note: If you have to add new flags to the enumeration, then don't
* forget to update %IEEE80211_TX_TEMPORARY_FLAGS when necessary.
next prev parent reply other threads:[~2011-01-06 21:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-06 21:36 [PATCH 0/4] some wireless doc updates Johannes Berg
2011-01-06 21:36 ` Johannes Berg [this message]
2011-01-06 21:36 ` [PATCH 2/4] cfg80211: add mesh join/leave callback docs Johannes Berg
2011-01-06 21:36 ` [PATCH 3/4] nl80211: add/fix mesh docs Johannes Berg
2011-01-06 21:36 ` [PATCH 4/4] mac80211: add doc short section on LED triggers 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=20110106213714.894284080@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=johannes.berg@intel.com \
--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).