From: Luca Coelho <luca@coelho.fi>
To: johannes@sipsolutions.net
Cc: linux-wireless@vger.kernel.org, andrei.otcheretianski@intel.com
Subject: [PATCH] cfg80211: add documentation for max_num_csa_coutners
Date: Thu, 15 May 2014 20:18:09 +0300 [thread overview]
Message-ID: <1400174289-22108-1-git-send-email-luca@coelho.fi> (raw)
From: Luciano Coelho <luciano.coelho@intel.com>
Move the comment in the structure to a description of the
max_num_csa_counters field in the docbook area.
This fixes a warning when building htmldocs (at least):
Warning(include/net/cfg80211.h:3064): No description found for parameter 'max_num_csa_counters'
Signed-off-by: Luciano Coelho <luciano.coelho@intel.com>
---
include/net/cfg80211.h | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/include/net/cfg80211.h b/include/net/cfg80211.h
index 447cb58..955fdec 100644
--- a/include/net/cfg80211.h
+++ b/include/net/cfg80211.h
@@ -2936,6 +2936,11 @@ struct wiphy_vendor_command {
* (including P2P GO) or 0 to indicate no such limit is advertised. The
* driver is allowed to advertise a theoretical limit that it can reach in
* some cases, but may not always reach.
+ *
+ * @max_num_csa_counters: Number of supported csa_counters in beacons
+ * and probe responses. This value should be set if the driver
+ * wishes to limit the number of csa counters. Default (0) means
+ * infinite.
*/
struct wiphy {
/* assign these fields before you register the wiphy */
@@ -3053,11 +3058,6 @@ struct wiphy {
u16 max_ap_assoc_sta;
- /*
- * Number of supported csa_counters in beacons and probe responses.
- * This value should be set if the driver wishes to limit the number of
- * csa counters. Default (0) means infinite.
- */
u8 max_num_csa_counters;
char priv[0] __aligned(NETDEV_ALIGN);
--
2.0.0.rc0
next reply other threads:[~2014-05-15 17:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-15 17:18 Luca Coelho [this message]
2014-05-19 12:40 ` [PATCH] cfg80211: add documentation for max_num_csa_coutners 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=1400174289-22108-1-git-send-email-luca@coelho.fi \
--to=luca@coelho.fi \
--cc=andrei.otcheretianski@intel.com \
--cc=johannes@sipsolutions.net \
--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 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).