From: Randy Dunlap <randy.dunlap@oracle.com>
To: linux-wireless@vger.kernel.org
Cc: linville@tuxdriver.com, johannes@sipsolutions.net
Subject: [PATCH] mac80211: fix more kernel-doc warnings
Date: Tue, 29 Jul 2008 20:59:16 -0700 [thread overview]
Message-ID: <20080729205916.c4c6c363.randy.dunlap@oracle.com> (raw)
From: Randy Dunlap <randy.dunlap@oracle.com>
Fix several kernel-doc warnings in mac80211 header files:
Warning(linux-2.6.27-rc1//include/net/mac80211.h:759): Enum value 'IEEE80211_HW_HOST_GEN_BEACON_TEMPLATE' not described in enum 'ieee80211_hw_flags'
Warning(linux-2.6.27-rc1//net/mac80211/sta_info.h:329): No description found for parameter 'tid_seq[IEEE80211_QOS_CTL_TID_MASK + 1]'
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
---
include/net/mac80211.h | 4 ++++
net/mac80211/sta_info.h | 1 +
2 files changed, 5 insertions(+)
--- linux-2.6.27-rc1.orig/include/net/mac80211.h
+++ linux-2.6.27-rc1/include/net/mac80211.h
@@ -700,6 +700,10 @@ enum ieee80211_tkip_key_type {
* any particular flags. There are some exceptions to this rule,
* however, so you are advised to review these flags carefully.
*
+ * @IEEE80211_HW_HOST_GEN_BEACON_TEMPLATE:
+ * Indicates that hardware or firmware takes care of beacon
+ * generation.
+ *
* @IEEE80211_HW_RX_INCLUDES_FCS:
* Indicates that received frames passed to the stack include
* the FCS at the end.
--- linux-2.6.27-rc1.orig/net/mac80211/sta_info.h
+++ linux-2.6.27-rc1/net/mac80211/sta_info.h
@@ -204,6 +204,7 @@ struct sta_ampdu_mlme {
* @tx_fragments: number of transmitted MPDUs
* @txrate_idx: TBD
* @last_txrate_idx: TBD
+ * @tid_seq: TBD
* @wme_tx_queue: TBD
* @ampdu_mlme: TBD
* @timer_to_tid: identity mapping to ID timers
next reply other threads:[~2008-07-30 4:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-30 3:59 Randy Dunlap [this message]
2008-07-30 6:46 ` [PATCH] mac80211: fix more kernel-doc warnings 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=20080729205916.c4c6c363.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--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