On Thu, 2014-07-24 at 14:21 +0200, Lorenzo Bianconi wrote: > Currently iw does not allow to set both attribute at the same time, > but I can use "if-else if" statement in order to exclude that > condition. I think you should explicitly reject the configuration if both attributes are given, not silently use one of them. > > You should also have a feature flag that drivers set that you test here > > and refuse dynamic if it's not supported, I guess? > > > > I would rely on lower drivers to fail (returning -EOPNOTSUPP to > set_coverage_class caller) if dynack it is not supported and user is > trying to enable it. Does it sound good for you? I imagined you'd want to know in 'iw list' whether or not it's supported too. johannes -- 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
