Return-path: Received: from s3.sipsolutions.net ([5.9.151.49]:49181 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751560AbcGRS4v (ORCPT ); Mon, 18 Jul 2016 14:56:51 -0400 Message-ID: <1468868209.2944.1.camel@sipsolutions.net> (sfid-20160718_205654_864339_82F93400) Subject: Re: [PATCH v2] cfg80211: Allow differnt beacon interval if driver supports From: Johannes Berg To: Purushottam Kushwaha Cc: linux-wireless@vger.kernel.org, jouni@qca.qualcomm.com, usdutt@qti.qualcomm.com, ganeshk@qti.qualcomm.com, mkalikot@qca.qualcomm.com, amarnath@qca.qualcomm.com Date: Mon, 18 Jul 2016 20:56:49 +0200 In-Reply-To: <1468849985-6881-1-git-send-email-pkushwah@qti.qualcomm.com> References: <1468849985-6881-1-git-send-email-pkushwah@qti.qualcomm.com> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Sender: linux-wireless-owner@vger.kernel.org List-ID: On Mon, 2016-07-18 at 19:23 +0530, Purushottam Kushwaha wrote: > Driver may allow support for different beacon interval on virtual > interfaces. > Allow if such support is advertised by driver. This adds new > ext_feature as NL80211_EXT_FEATURE_DIFF_BEACON_INTERVAL. We have NL80211_IFACE_COMB_STA_AP_BI_MATCH in interface combinations, perhaps it would make sense to also put this flag there? johannes