| developer | ec4ebe4 | 2022-04-12 11:17:45 +0800 | [diff] [blame] | 1 | ath10k-ct starting with version 5.2 allows the combination of |
| 2 | NL80211_IFTYPE_ADHOC and beacon_int_min_gcd in ath10k_10x_ct_if_comb |
| 3 | which triggers this warning. Ben told me that this is not a big problem |
| 4 | and we should ignore this. |
| 5 | |
| 6 | --- a/net/wireless/core.c |
| 7 | +++ b/net/wireless/core.c |
| developer | 0b3fe20 | 2022-04-19 10:19:57 +0800 | [diff] [blame^] | 8 | @@ -625,21 +625,6 @@ static int wiphy_verify_combinations(str |
| developer | ec4ebe4 | 2022-04-12 11:17:45 +0800 | [diff] [blame] | 9 | c->limits[j].max > 1)) |
| 10 | return -EINVAL; |
| 11 | |
| 12 | - /* |
| 13 | - * This isn't well-defined right now. If you have an |
| 14 | - * IBSS interface, then its beacon interval may change |
| 15 | - * by joining other networks, and nothing prevents it |
| 16 | - * from doing that. |
| 17 | - * So technically we probably shouldn't even allow AP |
| 18 | - * and IBSS in the same interface, but it seems that |
| 19 | - * some drivers support that, possibly only with fixed |
| 20 | - * beacon intervals for IBSS. |
| 21 | - */ |
| 22 | - if (WARN_ON(types & BIT(NL80211_IFTYPE_ADHOC) && |
| 23 | - c->beacon_int_min_gcd)) { |
| 24 | - return -EINVAL; |
| 25 | - } |
| 26 | - |
| 27 | cnt += c->limits[j].max; |
| 28 | /* |
| 29 | * Don't advertise an unsupported type |