On Tue, Mar 29, 2016 at 12:35:03PM +0300, Emmanuel Grumbach wrote: > Provide a function the driver can call to report a match. > This will send the event to the user space. > diff --git a/include/net/cfg80211.h b/include/net/cfg80211.h > +/** > + * struct cfg80211_nan_match_params - NAN match parameters > + * @type: the type of the function that triggered a match. If it is > + * %NL80211_NAN_FUNC_SUBSCRIBE it means that we replied to a subscriber. > + * If it is %NL80211_NAN_FUNC_PUBLISH, it means that we got a discovery > + * result. > + * If it is %NL80211_NAN_FUNC_FOLLOW_UP, we received a follow up. > +/** > + * cfg80211_nan_match - report a match for a NAN function. > + * @wdev: the wireless device reporting the match > + * @match: match notification parameters > + * @gfp: allocation flags > + * > + * This function reports that the a NAN function had a match. This > + * can be a subscribe that had a match or a solicited publish that > + * was sent. It can also be a follow up that was received. > + */ > +void cfg80211_nan_match(struct wireless_dev *wdev, > + struct cfg80211_nan_match_params *match, gfp_t gfp); Looks like this function is common for publish, subscribe and follow up. If so, can we please have separate functions for publish, subscribe and followup to match the spec primitives? -- Jouni Malinen PGP id EFC895FA-- 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
