Message ID | 20220713094502.163926-1-johannes@sipsolutions.net (mailing list archive) |
---|---|
Headers | show |
Series | wifi: more MLO work | expand |
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
On Thu, 2022-07-14 at 10:26 +0200, Arend Van Spriel wrote: > > 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? > Well, we had a discussion with Jakub, and he kind of indicated that he'd like to see a bit more generic prefixes to clarify things. We've kind of been early adopters to try it out and see what it looks like, he hasn't pushed it and wanted to have a discussion (e.g. at LPC or netdevconf) about it first, but it kind of makes sense since not everyone can know all the different drivers and components. johannes
Johannes Berg <johannes@sipsolutions.net> writes: > On Thu, 2022-07-14 at 10:26 +0200, Arend Van Spriel wrote: >> >> 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? >> > > Well, we had a discussion with Jakub, and he kind of indicated that he'd > like to see a bit more generic prefixes to clarify things. > > We've kind of been early adopters to try it out and see what it looks > like, he hasn't pushed it and wanted to have a discussion (e.g. at LPC > or netdevconf) about it first, but it kind of makes sense since not > everyone can know all the different drivers and components. I have been supposed to document this in the wiki and announce it properly, but as usual I was too busy before the vacation to do anything. And now I'm on vacation and trying to enjoy the 13 C of "warmth" here in Finland :D