Search Linux Wireless

[PATCH net] MAINTAINERS: exclude wireless drivers from netdev

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxxx>
---
CC: kvalo@xxxxxxxxxx
CC: johannes@xxxxxxxxxxxxxxxx
CC: linux-wireless@xxxxxxxxxxxxxxx

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
-- 
2.40.1




[Index of Archives]     [Linux Host AP]     [ATH6KL]     [Linux Wireless Personal Area Network]     [Linux Bluetooth]     [Wireless Regulations]     [Linux Netdev]     [Kernel Newbies]     [Linux Kernel]     [IDE]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite Hiking]     [MIPS Linux]     [ARM Linux]     [Linux RAID]

  Powered by Linux