Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <e9ecb9c8-cb5b-d727-38d6-ef5a0bf81cef@gmail.com>
Date:   Thu, 14 Jul 2022 10:26:37 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101
 Thunderbird/91.11.0
Subject: Re: [PATCH 00/76] wifi: more MLO work
Content-Language: en-US
To:     Johannes Berg <johannes@sipsolutions.net>,
        linux-wireless@vger.kernel.org
References: <20220713094502.163926-1-johannes@sipsolutions.net>
From:   Arend Van Spriel <aspriel@gmail.com>
In-Reply-To: <20220713094502.163926-1-johannes@sipsolutions.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk

On 7/13/2022 11:43 AM, Johannes Berg wrote:
> Hi,
> 
> So our MLO work is progressing. Internally, I have limited support
> for MLO connections now (over hwsim), but that's at least another
> 25 patches on top of this series.
> 
> But would be good to get things out first anyway. I'm tempted to
> just apply this (after net-next merges wireless-next and we will
> merge back) though - even if we have more fixes to it later.

Just for my own patch submit process. What is the reason I am seeing the 
"wifi:" prefix being used with patches on linux-wireless list? Is there 
other wireless tech used, eg. "bt:" or so?

Regards,
Arend