| 1234567891011121314151617181920212223242526272829 |
- ath10k-ct starting with version 5.2 allows the combination of
- NL80211_IFTYPE_ADHOC and beacon_int_min_gcd in ath10k_10x_ct_if_comb
- which triggers this warning. Ben told me that this is not a big problem
- and we should ignore this.
- --- a/net/wireless/core.c
- +++ b/net/wireless/core.c
- @@ -614,21 +614,6 @@ static int wiphy_verify_combinations(str
- c->limits[j].max > 1))
- return -EINVAL;
-
- - /*
- - * This isn't well-defined right now. If you have an
- - * IBSS interface, then its beacon interval may change
- - * by joining other networks, and nothing prevents it
- - * from doing that.
- - * So technically we probably shouldn't even allow AP
- - * and IBSS in the same interface, but it seems that
- - * some drivers support that, possibly only with fixed
- - * beacon intervals for IBSS.
- - */
- - if (WARN_ON(types & BIT(NL80211_IFTYPE_ADHOC) &&
- - c->beacon_int_min_gcd)) {
- - return -EINVAL;
- - }
- -
- cnt += c->limits[j].max;
- /*
- * Don't advertise an unsupported type
|
