|
52 | 52 | * such wiphy can have zero, one, or many virtual interfaces associated with
|
53 | 53 | * it, which need to be identified as such by pointing the network interface's
|
54 | 54 | * @ieee80211_ptr pointer to a &struct wireless_dev which further describes
|
55 |
| - * the wireless part of the interface, normally this struct is embedded in the |
| 55 | + * the wireless part of the interface. Normally this struct is embedded in the |
56 | 56 | * network interface's private data area. Drivers can optionally allow creating
|
57 | 57 | * or destroying virtual interfaces on the fly, but without at least one or the
|
58 | 58 | * ability to create some the wireless device isn't useful.
|
@@ -2584,7 +2584,7 @@ struct cfg80211_scan_info {
|
2584 | 2584 | * @short_ssid: short ssid to scan for
|
2585 | 2585 | * @bssid: bssid to scan for
|
2586 | 2586 | * @channel_idx: idx of the channel in the channel array in the scan request
|
2587 |
| - * which the above info relvant to |
| 2587 | + * which the above info is relevant to |
2588 | 2588 | * @unsolicited_probe: the AP transmits unsolicited probe response every 20 TU
|
2589 | 2589 | * @short_ssid_valid: @short_ssid is valid and can be used
|
2590 | 2590 | * @psc_no_listen: when set, and the channel is a PSC channel, no need to wait
|
@@ -7504,7 +7504,7 @@ void cfg80211_notify_new_peer_candidate(struct net_device *dev,
|
7504 | 7504 | * RFkill integration in cfg80211 is almost invisible to drivers,
|
7505 | 7505 | * as cfg80211 automatically registers an rfkill instance for each
|
7506 | 7506 | * wireless device it knows about. Soft kill is also translated
|
7507 |
| - * into disconnecting and turning all interfaces off, drivers are |
| 7507 | + * into disconnecting and turning all interfaces off. Drivers are |
7508 | 7508 | * expected to turn off the device when all interfaces are down.
|
7509 | 7509 | *
|
7510 | 7510 | * However, devices may have a hard RFkill line, in which case they
|
@@ -7552,7 +7552,7 @@ static inline void wiphy_rfkill_stop_polling(struct wiphy *wiphy)
|
7552 | 7552 | * the configuration mechanism.
|
7553 | 7553 | *
|
7554 | 7554 | * A driver supporting vendor commands must register them as an array
|
7555 |
| - * in struct wiphy, with handlers for each one, each command has an |
| 7555 | + * in struct wiphy, with handlers for each one. Each command has an |
7556 | 7556 | * OUI and sub command ID to identify it.
|
7557 | 7557 | *
|
7558 | 7558 | * Note that this feature should not be (ab)used to implement protocol
|
@@ -7716,7 +7716,7 @@ static inline void cfg80211_vendor_event(struct sk_buff *skb, gfp_t gfp)
|
7716 | 7716 | * interact with driver-specific tools to aid, for instance,
|
7717 | 7717 | * factory programming.
|
7718 | 7718 | *
|
7719 |
| - * This chapter describes how drivers interact with it, for more |
| 7719 | + * This chapter describes how drivers interact with it. For more |
7720 | 7720 | * information see the nl80211 book's chapter on it.
|
7721 | 7721 | */
|
7722 | 7722 |
|
|
0 commit comments