Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::3:3 as permitted sender) client-ip=2620:137:e000::3:3;
Message-ID: <90fcfe15-de1b-4371-a316-574ac7a03eda@quicinc.com>
Date:   Fri, 6 Oct 2023 16:15:46 -0700
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: removing OCB/WAVE/802.11p
Content-Language: en-US
To:     Johannes Berg <johannes@sipsolutions.net>,
        <linux-wireless@vger.kernel.org>
CC:     Rostislav Lisovy <lisovy@gmail.com>,
        Bertold Van den Bergh <bertold.vandenbergh@esat.kuleuven.be>,
        <chrisshen@skku.edu>, <bienaime@skku.edu>, <pauljeong@skku.edu>,
        <carloaugusto.grazia@unimore.it>
References: <ec69aa2722b07bffd6184d687861cc7e5ae9c1ef.camel@sipsolutions.net>
From:   Jeff Johnson <quic_jjohnson@quicinc.com>
In-Reply-To: <ec69aa2722b07bffd6184d687861cc7e5ae9c1ef.camel@sipsolutions.net>
Content-Type: text/plain; charset="UTF-8"; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk

On 9/28/2023 8:38 AM, Johannes Berg wrote:
> Hi,
> 
> CC'ing lots of people who touched or used this in the past in hopes of
> triggering some reaction somewhere ...
> 
> I'm trying to do some cleanup in IBSS and following that some other
> cleanups wrt. station allocation etc., but OCB pretty much copied the
> IBSS code in this area, and I don't know how to use it, how to test it,
> who's using it, if anyone is actually maintaining it, etc.
> 
> Also, it only ever got implemented for ath9k, so I'm guessing it's not
> getting any traction in new products/devices.
> 
> So I'm probably going to remove it.
> 
> Any takers to help maintain it instead?

Do you have an estimate on the footprint of this logic? Do you have a 
proposed patch?

In addition to ath9k I know there is out-of-tree usage of this 
functionality, and I'm trying to see if I can find someone to maintain 
this. But how would that actually work?

/jeff