From: Jakub Kicinski <kuba@kernel.org>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, edumazet@google.com, pabeni@redhat.com,
Jakub Kicinski <kuba@kernel.org>,
kvalo@kernel.org, johannes@sipsolutions.net,
linux-wireless@vger.kernel.org
Subject: [PATCH net] MAINTAINERS: exclude wireless drivers from netdev
Date: Thu, 11 May 2023 09:03:10 -0700 [thread overview]
Message-ID: <20230511160310.979113-1-kuba@kernel.org> (raw)
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@kernel.org>
---
CC: kvalo@kernel.org
CC: johannes@sipsolutions.net
CC: linux-wireless@vger.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¶m=-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
next reply other threads:[~2023-05-11 16:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-11 16:03 Jakub Kicinski [this message]
2023-05-11 16:38 ` [PATCH net] MAINTAINERS: exclude wireless drivers from netdev Johannes Berg
2023-05-12 4:06 ` Kalle Valo
2023-05-11 16:50 ` Marcel Holtmann
2023-05-11 23:45 ` Jakub Kicinski
2023-05-12 8:00 ` patchwork-bot+netdevbpf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230511160310.979113-1-kuba@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=johannes@sipsolutions.net \
--cc=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.