Make the driver responsible for making sure it is capable of performing the switch. It might as well accept a request but then disconnect an interface if some requirements are not met. In that case userspace should be prepared for an appropriate event (AP/IBSS/mesh being stopped/left). Signed-off-by: Michal Kazior <michal.kazior@xxxxxxxxx> --- net/wireless/nl80211.c | 11 ----------- 1 file changed, 11 deletions(-) diff --git a/net/wireless/nl80211.c b/net/wireless/nl80211.c index 5465e0e..6b7ded9 100644 --- a/net/wireless/nl80211.c +++ b/net/wireless/nl80211.c @@ -5921,17 +5921,6 @@ skip_beacons: params.radar_required = true; } - /* TODO: I left this here for now. With channel switch, the - * verification is a bit more complicated, because we only do - * it later when the channel switch really happens. - */ - err = cfg80211_can_use_iftype_chan(rdev, wdev, wdev->iftype, - params.chandef.chan, - CHAN_MODE_SHARED, - radar_detect_width); - if (err) - return err; - if (info->attrs[NL80211_ATTR_CH_SWITCH_BLOCK_TX]) params.block_tx = true; -- 1.8.5.3 -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
