lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 14 Jul 2022 10:30:19 +0200
From:   Johannes Berg <johannes@...solutions.net>
To:     Arend Van Spriel <aspriel@...il.com>,
        linux-wireless@...r.kernel.org, kvalo@...nel.org,
        Jakub Kicinski <kuba@...nel.org>
Cc:     netdev@...r.kernel.org
Subject: Re: [PATCH 00/76] wifi: more MLO work

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ