Message ID | 1447349791-3849-1-git-send-email-poh@qca.qualcomm.com (mailing list archive) |
---|---|
State | Not Applicable |
Headers | show |
On Thu, 2015-11-12 at 09:36 -0800, Peter Oh wrote: > Add NL80211_EXT_FEATURE_VHT_MESH flag to allow drivers > to indicate support for VHT in Mesh mode. > I'm confused. Why would it be needed? You haven't added any API or anything where userspace would do something differently based on whether or not it's supported? There's nothing checking the flag, so where's the point? johannes
diff --git a/include/uapi/linux/nl80211.h b/include/uapi/linux/nl80211.h index 1f0b4cf..4a16ed5 100644 --- a/include/uapi/linux/nl80211.h +++ b/include/uapi/linux/nl80211.h @@ -4389,12 +4389,14 @@ enum nl80211_feature_flags { /** * enum nl80211_ext_feature_index - bit index of extended features. * @NL80211_EXT_FEATURE_VHT_IBSS: This driver supports IBSS with VHT datarates. + * @NL80211_EXT_FEATURE_VHT_MESH: This driver supports Mesh with VHT datarates. * * @NUM_NL80211_EXT_FEATURES: number of extended features. * @MAX_NL80211_EXT_FEATURES: highest extended feature index. */ enum nl80211_ext_feature_index { NL80211_EXT_FEATURE_VHT_IBSS, + NL80211_EXT_FEATURE_VHT_MESH, /* add new features before the definition below */ NUM_NL80211_EXT_FEATURES,
Add NL80211_EXT_FEATURE_VHT_MESH flag to allow drivers to indicate support for VHT in Mesh mode. Signed-off-by: Peter Oh <poh@qca.qualcomm.com> --- include/uapi/linux/nl80211.h | 2 ++ 1 file changed, 2 insertions(+)