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 08/10] cfg80211: merge documentations of field "dev"
Date: Fri, 21 Feb 2020 12:56:02 +0100	[thread overview]
Message-ID: <20200221115604.594035-8-Jerome.Pouiller@silabs.com> (raw)
In-Reply-To: <20200221115604.594035-1-Jerome.Pouiller@silabs.com>

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

The field "dev" was documented on two places. This patch merges the
comments.

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

diff --git a/include/net/cfg80211.h b/include/net/cfg80211.h
index 2bb963e96c32..1cc3442b540f 100644
--- a/include/net/cfg80211.h
+++ b/include/net/cfg80211.h
@@ -4411,7 +4411,9 @@ struct cfg80211_pmsr_capabilities {
  *	unregister hardware
  * @debugfsdir: debugfs directory used for this wiphy (ieee80211/<wiphyname>).
  *	It will be renamed automatically on wiphy renames
- * @dev: (virtual) struct device for this wiphy
+ * @dev: (virtual) struct device for this wiphy. The item in
+ *	/sys/class/ieee80211/ points to this. You need use set_wiphy_dev()
+ *	(see below).
  * @wext: wireless extension handlers
  * @priv: driver private data (sized according to wiphy_new() parameter)
  * @interface_modes: bitmask of interfaces types valid for this wiphy,
@@ -4633,8 +4635,6 @@ struct wiphy {
 
 	const struct ieee80211_regdomain __rcu *regd;
 
-	/* the item in /sys/class/ieee80211/ points to this,
-	 * you need use set_wiphy_dev() (see below) */
 	struct device dev;
 
 	bool registered;
-- 
2.25.0


  parent reply	other threads:[~2020-02-21 11:56 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 ` Jerome Pouiller [this message]
2020-02-21 11:56 ` [PATCH 09/10] cfg80211: align documentation style of ieee80211_iface_combination Jerome Pouiller
2020-02-21 12:02   ` 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-8-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).