linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jerome Pouiller <Jerome.Pouiller@silabs.com>
To: linux-wireless@vger.kernel.org
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Jakub Kicinski" <kuba@kernel.org>,
	"Johannes Berg" <johannes@sipsolutions.net>,
	"David S . Miller" <davem@davemloft.net>,
	"Jérôme Pouiller" <jerome.pouiller@silabs.com>
Subject: [PATCH 09/10] cfg80211: align documentation style of ieee80211_iface_combination
Date: Fri, 21 Feb 2020 12:56:03 +0100	[thread overview]
Message-ID: <20200221115604.594035-9-Jerome.Pouiller@silabs.com> (raw)
In-Reply-To: <20200221115604.594035-1-Jerome.Pouiller@silabs.com>

From: Jérôme Pouiller <jerome.pouiller@silabs.com>

In cfg80211.h, all the structs but ieee80211_iface_combination are
documented above their definition.

Signed-off-by: Jérôme Pouiller <jerome.pouiller@silabs.com>
---
 include/net/cfg80211.h | 63 +++++++++++-------------------------------
 1 file changed, 16 insertions(+), 47 deletions(-)

diff --git a/include/net/cfg80211.h b/include/net/cfg80211.h
index 1cc3442b540f..2f8c41993ed2 100644
--- a/include/net/cfg80211.h
+++ b/include/net/cfg80211.h
@@ -4103,62 +4103,31 @@ struct ieee80211_iface_limit {
  *		.num_different_channels = 2,
  *	};
  *
+ * @limits: limits for the given interface types
+ * @num_different_channels: can use up to this many different channels
+ * @max_interfaces:  maximum number of interfaces in total allowed in this group
+ * @n_limits: number of limitations
+ * @beacon_int_infra_match: In this combination, the beacon intervals between
+ *	infrastructure and AP types must match. This is required only in special
+ *	cases.
+ * @radar_detect_widths: bitmap of channel widths supported for radar detection
+ * @radar_detect_regions: bitmap of regions supported for radar detection
+ * @beacon_int_min_gcd: This interface combination supports different beacon
+ *	intervals:
+ *	    * = 0: all beacon intervals for different interface must be same.
+ *	    * > 0: any beacon interval for the interface part of this
+ *	      combination AND GCD of all beacon intervals from beaconing
+ *	      interfaces of this combination must be greater or equal to this
+ *	      value.
  */
 struct ieee80211_iface_combination {
-	/**
-	 * @limits:
-	 * limits for the given interface types
-	 */
 	const struct ieee80211_iface_limit *limits;
-
-	/**
-	 * @num_different_channels:
-	 * can use up to this many different channels
-	 */
 	u32 num_different_channels;
-
-	/**
-	 * @max_interfaces:
-	 * maximum number of interfaces in total allowed in this group
-	 */
 	u16 max_interfaces;
-
-	/**
-	 * @n_limits:
-	 * number of limitations
-	 */
 	u8 n_limits;
-
-	/**
-	 * @beacon_int_infra_match:
-	 * In this combination, the beacon intervals between infrastructure
-	 * and AP types must match. This is required only in special cases.
-	 */
 	bool beacon_int_infra_match;
-
-	/**
-	 * @radar_detect_widths:
-	 * bitmap of channel widths supported for radar detection
-	 */
 	u8 radar_detect_widths;
-
-	/**
-	 * @radar_detect_regions:
-	 * bitmap of regions supported for radar detection
-	 */
 	u8 radar_detect_regions;
-
-	/**
-	 * @beacon_int_min_gcd:
-	 * This interface combination supports different beacon intervals.
-	 *
-	 * = 0
-	 *   all beacon intervals for different interface must be same.
-	 * > 0
-	 *   any beacon interval for the interface part of this combination AND
-	 *   GCD of all beacon intervals from beaconing interfaces of this
-	 *   combination must be greater or equal to this value.
-	 */
 	u32 beacon_int_min_gcd;
 };
 
-- 
2.25.0


  parent reply	other threads:[~2020-02-21 11:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-21 11:55 [PATCH 01/10] cfg80211: drop duplicated documentation of field "probe_resp_offload" Jerome Pouiller
2020-02-21 11:55 ` [PATCH 02/10] cfg80211: drop duplicated documentation of field "privid" Jerome Pouiller
2020-02-21 11:55 ` [PATCH 03/10] cfg80211: drop duplicated documentation of field "registered" Jerome Pouiller
2020-02-21 11:55 ` [PATCH 04/10] cfg80211: drop duplicated documentation of field "_net" Jerome Pouiller
2020-02-21 11:55 ` [PATCH 05/10] cfg80211: drop duplicated documentation of field "perm_addr" Jerome Pouiller
2020-02-21 11:56 ` [PATCH 06/10] cfg80211: drop duplicated documentation of field "reg_notifier" Jerome Pouiller
2020-02-21 11:56 ` [PATCH 07/10] cfg80211: merge documentations of field "debugfsdir" Jerome Pouiller
2020-02-21 11:56 ` [PATCH 08/10] cfg80211: merge documentations of field "dev" Jerome Pouiller
2020-02-21 11:56 ` Jerome Pouiller [this message]
2020-02-21 12:02   ` [PATCH 09/10] cfg80211: align documentation style of ieee80211_iface_combination Johannes Berg
2020-02-21 12:38     ` Jérôme Pouiller
2020-02-21 12:41       ` Johannes Berg
2020-02-21 12:49         ` Jérôme Pouiller
2020-02-21 11:56 ` [PATCH 10/10] cfg80211: fix indentation errors Jerome Pouiller

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=20200221115604.594035-9-Jerome.Pouiller@silabs.com \
    --to=jerome.pouiller@silabs.com \
    --cc=davem@davemloft.net \
    --cc=johannes@sipsolutions.net \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@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).