On Wed, Jun 11, 2014 at 12:44 AM, Luis R. Rodriguez <mcgrof@xxxxxxxxxxxxxxxx> wrote: > > On Tue, May 20, 2014 at 1:48 AM, Luis R. Rodriguez > <mcgrof@xxxxxxxxxxxxxxxx> wrote: > > On Sun, May 11, 2014 at 1:50 AM, Emmanuel Grumbach > > <emmanuel.grumbach@xxxxxxxxx> wrote: > >> Hi Johannes, > >> > >> Newer Intel cards store regulatory settings in firmware. > >> This patch series adds support for a wiphy callback, allowing > >> the regulatory core to fetch driver/firmware defined redgomain > >> data whenever a country code change is requested. > >> > >> Along with that, there is also a small fix from Eliad. > >> > >> Arik Nemtsov (6): > >> cfg80211: don't set reg timeout for user-handled hint > >> cfg80211: introduce regulatory flags controlling bw > >> cfg80211: allow drivers to provide regulatory settings > >> cfg80211: treat the special "unknown" alpha2 as valid > >> cfg80211: accept world/same regdom from driver/user hints > >> cfg80211: leave invalid channels on regdomain change > > > > Please Cc me on regulatory patches. I've noted issues with the wiphy > > callback addition, but other than place if you can please resend > > patches that do not depend on that, that'd be appreciated, I'll take a > > look at those in the morning. > > I haven't seen these patches, please split them up, I think a few > already were accepted, but separating them between the new > functionality being added is key to speedy review. I'll take a second > stab at review of the fw API now as I'm going comfortalbe with the > idea of letting folks shoot themselves on the foot. This one is in, it's an obvious fix: 4d3df54 cfg80211: don't set reg timeout for user-handled hint The others are patches supporting the new Intel regulatory solution, so none of them are in. I'll make sure to resend them today. Arik -- 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
