On Thu, 2014-11-13 at 18:13 +0200, Arik Nemtsov wrote: > When the regulatory settings change, some channels might become invalid. > Disconnect interfaces acting on these channels, after giving userspace > code a grace period to leave them.
So as we discussed, I think you should add a note here that the flag only works for some interface types, and prohibit setting the flag when unsupported ones are supported. Then you can also remove the message and just put in a WARN_ON(1) or something since you can't really get to that code path. IMHO that's a reasonable trade-off between generalisation and not doing all the work now especially since you can't validate it over Intel hw for other interface types - if anyone else needs/wants the flag then they can add those interface types and change the conditions. johannes -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
