netdev - Re: [PATCH net] MAINTAINERS: exclude wireless drivers from netdev

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-prev] [thread-next>] [day] [month] [year] [list]

Date: Thu, 11 May 2023 18:50:15 +0200
From: Marcel Holtmann <marcel@...tmann.org>
To: Jakub Kicinski <kuba@...nel.org>
Cc: "David S. Miller" <davem@...emloft.net>,
 netdev <netdev@...r.kernel.org>,
 Eric Dumazet <edumazet@...gle.com>,
 Paolo Abeni <pabeni@...hat.com>,
 kvalo@...nel.org,
 Johannes Berg <johannes@...solutions.net>,
 linux-wireless@...r.kernel.org
Subject: Re: [PATCH net] MAINTAINERS: exclude wireless drivers from netdev

Hi Jakub,

> It seems that we mostly get netdev CCed on wireless patches
> which are written by people who don't know any better and
> CC everything that get_maintainers spits out. Rather than
> patches which indeed could benefit from general networking
> review.
> 
> Marking them down in patchwork as Awaiting Upstream is
> a bit tedious.
> 
> Signed-off-by: Jakub Kicinski <kuba@...nel.org>
> ---
> CC: kvalo@...nel.org
> CC: johannes@...solutions.net
> CC: linux-wireless@...r.kernel.org
> 
> Is this okay with everyone?
> 
> It's not a big deal, but it really feels that for wireless
> we only get bot/autogenerated patches to netdev..
> 
> Here's the list of patches we marked as Awaiting Upstream:
> https://patchwork.kernel.org/project/netdevbpf/list/?delegate=netdev&param=-date&order=date&state=8
> ---
> MAINTAINERS | 1 +
> 1 file changed, 1 insertion(+)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 58239fbc7007..4c49f4703a18 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -14565,6 +14565,7 @@ T:	git git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git
> F:	Documentation/devicetree/bindings/net/
> F:	drivers/connector/
> F:	drivers/net/
> +X:	drivers/net/wireless/
> F:	include/dt-bindings/net/
> F:	include/linux/etherdevice.h
> F:	include/linux/fcdevice.h

I didn’t know such an option existed, can we do the same for Bluetooth?

Regards

Marcel