On Wed, Feb 19, 2014 at 05:39:36PM +0200, Ilan Peer wrote: > diff --git a/net/wireless/reg.c b/net/wireless/reg.c > index 8f5b460..b3768c2 100644 > --- a/net/wireless/reg.c > +++ b/net/wireless/reg.c > @@ -65,11 +65,24 @@ > #define REG_DBG_PRINT(args...) > #endif > > +/** > + * enum reg_request_treatment - regulatory request treatment > + * > + * @REG_REQ_OK: continue processing the regulatory request > + * @REG_REQ_IGNORE: ignore the regulatory request > + * @REG_REQ_INTERSECT: the regulatory domain resulting from this request should > + * be intersected with the current one. > + * @REG_REQ_ALREADY_SET: the regulatory request will not change the current > + * regulatory settings, and no further processing is required. > + * @REG_REQ_USER_HINT_HANDLED: a non alpha2 user hint was handled and no > + * further processing is required. May be worth expanding on this to clarify why you mention non alpha2, that is: regulatory hints that are not providing an alpha2 hint can use this to let the regulatory core know it won't need to consider the updating the last_request. Come to think of it, it gets me wondering if we can eventually just then move beacon hints to use this later. Luis -- 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
