Return-path: Received: from mail-wm0-f66.google.com ([74.125.82.66]:35342 "EHLO mail-wm0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751445AbdBJHOr (ORCPT ); Fri, 10 Feb 2017 02:14:47 -0500 MIME-Version: 1.0 In-Reply-To: <87tw82il32.fsf@kamboji.qca.qualcomm.com> References: <1486030773-30600-1-git-send-email-amadeusz.slawinski@tieto.com> <87y3xi4b28.fsf@qca.qualcomm.com> <5899DDD7.7000605@candelatech.com> <87tw82il32.fsf@kamboji.qca.qualcomm.com> From: Adrian Chadd Date: Thu, 9 Feb 2017 23:14:40 -0800 Message-ID: (sfid-20170210_081523_313156_7F36D60C) Subject: Re: [PATCH 1/3] ath10k: remove ath10k_vif_to_arvif() To: "Valo, Kalle" Cc: Ben Greear , "netdev@vger.kernel.org" , "linux-wireless@vger.kernel.org" , =?UTF-8?B?QW1hZGV1c3ogU8WCYXdpxYRza2k=?= , "ath10k@lists.infradead.org" , Linux Kernel Mailing List Content-Type: text/plain; charset=UTF-8 Sender: linux-wireless-owner@vger.kernel.org List-ID: On 9 February 2017 at 23:03, Valo, Kalle wrote: > Ben Greear writes: > >> On 02/07/2017 01:14 AM, Valo, Kalle wrote: >>> Adrian Chadd writes: >>> >>>> Removing this method makes the diff to FreeBSD larger, as "vif" in >>>> FreeBSD is a different pointer. >>>> >>>> (Yes, I have ath10k on freebsd working and I'd like to find a way to >>>> reduce the diff moving forward.) >>> >>> I don't like this "(void *) vif->drv_priv" style that much either but >>> apparently it's commonly used in Linux wireless code and already parts >>> of ath10k. So this patch just unifies the coding style. >> >> Surely the code compiles to the same thing, so why add a patch that >> makes it more difficult for Adrian and makes the code no easier to read >> for the rest of us? > > Because that's the coding style used already in Linux. It's great to see > that parts of ath10k can be used also in other systems but in principle > I'm not very fond of the idea starting to reject valid upstream patches > because of driver forks. > > I think backports project is doing it right, it's not limiting upstream > development in any way and handles all the API changes internally. Maybe > FreeBSD could do something similar? I tried, but ... well, imagine renaming vif->drv_priv to something else. That's what you're suggesting. :-) You can do it with coccinelle, but not via just backports API implementations. I'm a big fan of light weight accessor APIs for the same reason. (Since FreeBSD doesn't have that pointer in ieee80211vap, it's done a different way.) If you could convert other direct uses over to ath10k_vif_to_arvif() then that'd make me happier. If not, it's fine, when I push this into freebsd and fast-forward commits, I'll have to just maintain it. For what it's worth - the linux skb accessors are the same. If there were accessors for the skb data / len fields (like we do for mbufs) then porting the code would've involved about 5,000 less changed lines. -adrian