From: Maxime Chevallier <maxime.chevallier@bootlin.com>
To: davem@davemloft.net, Andrew Lunn <andrew@lunn.ch>,
Jakub Kicinski <kuba@kernel.org>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Heiner Kallweit <hkallweit1@gmail.com>
Cc: Maxime Chevallier <maxime.chevallier@bootlin.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
thomas.petazzoni@bootlin.com,
Russell King <linux@armlinux.org.uk>,
Simon Horman <horms@kernel.org>
Subject: [PATCH net-next] MAINTAINERS: Add dedicated entries for phy_link_topology
Date: Thu, 13 Mar 2025 16:30:06 +0100 [thread overview]
Message-ID: <20250313153008.112069-1-maxime.chevallier@bootlin.com> (raw)
The infrastructure to handle multi-phy devices is fairly standalone.
Add myself as maintainer for that part as well as the netlink uAPI
that exposes it.
Signed-off-by: Maxime Chevallier <maxime.chevallier@bootlin.com>
---
MAINTAINERS | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index ffbcd072fb14..7d878c62e67d 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -16491,6 +16491,13 @@ F: net/ethtool/mm.c
F: tools/testing/selftests/drivers/net/hw/ethtool_mm.sh
K: ethtool_mm
+NETWORKING [ETHTOOL PHY TOPOLOGY]
+M: Maxime Chevallier <maxime.chevallier@bootlin.com>
+F: Documentation/networking/phy-link-topology.rst
+F: drivers/net/phy/phy_link_topology.c
+F: include/linux/phy_link_topology.h
+F: net/ethtool/phy.c
+
NETWORKING [GENERAL]
M: "David S. Miller" <davem@davemloft.net>
M: Eric Dumazet <edumazet@google.com>
--
2.48.1
next reply other threads:[~2025-03-13 15:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-13 15:30 Maxime Chevallier [this message]
2025-03-17 21:17 ` [PATCH net-next] MAINTAINERS: Add dedicated entries for phy_link_topology Andrew Lunn
2025-03-21 16:05 ` Paolo Abeni
2025-03-21 17:37 ` Maxime Chevallier
2025-03-24 12:15 ` Jakub Kicinski
2025-03-27 10:43 ` Maxime Chevallier
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=20250313153008.112069-1-maxime.chevallier@bootlin.com \
--to=maxime.chevallier@bootlin.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=thomas.petazzoni@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox