Re: [PATCH] cfg80211: avoid intersection when applying custom reg

2014-12-14 Thread Arik Nemtsov
On Fri, Dec 12, 2014 at 2:41 PM, Johannes Berg johan...@sipsolutions.net wrote: On Sun, 2014-12-07 at 18:03 +0200, Arik Nemtsov wrote: The custom-reg handling function can currently only add flags to a given channel. This results in stale flags being left applied. In some cases a channel

Re: [PATCH] cfg80211: avoid intersection when applying custom reg

2014-12-12 Thread Johannes Berg
On Sun, 2014-12-07 at 18:03 +0200, Arik Nemtsov wrote: The custom-reg handling function can currently only add flags to a given channel. This results in stale flags being left applied. In some cases a channel was disabled and even the orig_flags were changed to reflect this. Previously the

Re: [PATCH] cfg80211: avoid intersection when applying custom reg

2014-12-12 Thread Luis R. Rodriguez
On Sun, Dec 07, 2014 at 06:03:45PM +0200, Arik Nemtsov wrote: The custom-reg handling function can currently only add flags to a given channel. This results in stale flags being left applied. In some cases a channel was disabled and even the orig_flags were changed to reflect this.

[PATCH] cfg80211: avoid intersection when applying custom reg

2014-12-07 Thread Arik Nemtsov
The custom-reg handling function can currently only add flags to a given channel. This results in stale flags being left applied. In some cases a channel was disabled and even the orig_flags were changed to reflect this. Previously the API was designed for a single invocation before wiphy