[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250204215750.169249-1-kuba@kernel.org>
Date: Tue, 4 Feb 2025 13:57:50 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: davem@...emloft.net
Cc: netdev@...r.kernel.org,
edumazet@...gle.com,
pabeni@...hat.com,
andrew+netdev@...n.ch,
horms@...nel.org,
Jakub Kicinski <kuba@...nel.org>
Subject: [PATCH net v2 2/2] MAINTAINERS: add a sample ethtool section entry
I feel like we don't do a good enough keeping authors of driver
APIs around. The ethtool code base was very nicely compartmentalized
by Michal. Establish a precedent of creating MAINTAINERS entries
for "sections" of the ethtool API. Use Andrew and cable test as
a sample entry. The entry should ideally cover 3 elements:
a core file, test(s), and keywords. The last one is important
because we intend the entries to cover core code *and* reviews
of drivers implementing given API!
Signed-off-by: Jakub Kicinski <kuba@...nel.org>
---
v2:
- use cable_test as the keyword, looks like it doesn't produce any
false positives
v1: https://lore.kernel.org/20250202021155.1019222-2-kuba@kernel.org
---
MAINTAINERS | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 20c8daf3ce62..bd705e9123a3 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -16465,6 +16465,12 @@ F: include/uapi/linux/ethtool*
F: net/ethtool/
F: tools/testing/selftests/drivers/net/*/ethtool*
+NETWORKING [ETHTOOL CABLE TEST]
+M: Andrew Lunn <andrew@...n.ch>
+F: net/ethtool/cabletest.c
+F: tools/testing/selftests/drivers/net/*/ethtool*
+K: cable_test
+
NETWORKING [GENERAL]
M: "David S. Miller" <davem@...emloft.net>
M: Eric Dumazet <edumazet@...gle.com>
--
2.48.1
Powered by blists - more mailing lists