From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from s3.sipsolutions.net ([5.9.151.49] helo=sipsolutions.net) by bombadil.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1YHB9i-00088k-8w for ath10k@lists.infradead.org; Fri, 30 Jan 2015 12:58:38 +0000 Message-ID: <1422622694.1919.17.camel@sipsolutions.net> Subject: Re: [PATCH v2 2/7] ath10k: implement chanctx API From: Johannes Berg Date: Fri, 30 Jan 2015 13:58:14 +0100 In-Reply-To: <1422621086-28970-3-git-send-email-michal.kazior@tieto.com> (sfid-20150130_133341_121083_F7682B5B) References: <1422607287-12289-1-git-send-email-michal.kazior@tieto.com> <1422621086-28970-1-git-send-email-michal.kazior@tieto.com> <1422621086-28970-3-git-send-email-michal.kazior@tieto.com> (sfid-20150130_133341_121083_F7682B5B) Mime-Version: 1.0 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "ath10k" Errors-To: ath10k-bounces+kvalo=adurom.com@lists.infradead.org To: Michal Kazior Cc: linux-wireless@vger.kernel.org, ath10k@lists.infradead.org > +++ b/drivers/net/wireless/ath/ath10k/core.h > @@ -277,6 +282,7 @@ struct ath10k_vif { > dma_addr_t beacon_paddr; > > struct ath10k *ar; > + struct ath10k_chanctx *arctx; you also have vif->chanctx_conf pointer, which you could use ultimately it's a software architecture decision - personally I wouldn't want to duplicate all that data and the lists etc. in the driver when mac80211 has them, but that's just my opinion. :) johannes _______________________________________________ ath10k mailing list ath10k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath10k