On Thu, 2014-02-13 at 12:00 +0200, Arik Nemtsov wrote: > It's fine. But I guess it's nicer to add a small ieee80211 wrapper for > it that also clears local->napi? not sure. Well if the whole thing is going down there's little point in that. > In general can we even add/remove napi when an interface is up or is > it a bad idea? if it is, maybe it should be warned/blocked? I guess > the scoping wasn't really clear for me, but maybe it is for anyone > familiar with napi. It seems that isn't allowed, the locking would seem rather missing for that? *Maybe* if the driver locks everything, but even then I'd be wary. 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
