From: Cunhao Lu via B4 Relay <devnull+1579567540.qq.com@kernel.org>
To: Jakub Kicinski <kuba@kernel.org>, netdev@vger.kernel.org
Cc: davem@davemloft.net, edumazet@kernel.org, pabeni@redhat.com,
horms@kernel.org, mkl@pengutronix.de, mailhol@kernel.org,
socketcan@hartkopp.net, robin@protonic.nl,
o.rempel@pengutronix.de, kernel@pengutronix.de, max@enpas.org,
linux-can@vger.kernel.org, linux-kernel@vger.kernel.org,
Cunhao Lu <1579567540@qq.com>
Subject: [PATCH net v2] MAINTAINERS: exclude CAN documentation from general networking
Date: Fri, 13 Nov 2026 10:33:06 +0800 [thread overview]
Message-ID: <20261113-exclude-can-docs-from-netdev-v2-1-8ae9dc553024@qq.com> (raw)
From: Cunhao Lu <1579567540@qq.com>
The SocketCAN, ISO-TP and J1939 documents and the CAN driver documentation
directory match the broad Documentation/networking/ pattern in
NETWORKING [GENERAL]. This makes get_maintainer.pl select netdev and the
general networking maintainers for these CAN-specific documentation
changes.
Exclude these paths from NETWORKING [GENERAL], as is already done for
net/can/ and the CAN selftests. Add the driver documentation directory
to CAN NETWORK DRIVERS to cover files without a dedicated CAN entry.
Suggested-by: Jakub Kicinski <kuba@kernel.org>
Link: https://lore.kernel.org/all/20261111161459.4879a82d@kernel.org/
Signed-off-by: Cunhao Lu <1579567540@qq.com>
---
Changes in v2:
- Exclude the whole CAN driver documentation directory instead of only
can327.rst, and add it to CAN NETWORK DRIVERS.
- Link to v1: https://patch.msgid.link/20261112-exclude-can-docs-from-netdev-v1-1-b5eb3ba4ae86@qq.com
---
MAINTAINERS | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 222b7fc2c3aa..152771314140 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -5992,6 +5992,7 @@ T: git git://git.kernel.org/pub/scm/linux/kernel/git/mkl/linux-can.git
T: git git://git.kernel.org/pub/scm/linux/kernel/git/mkl/linux-can-next.git
F: Documentation/devicetree/bindings/net/can/
F: Documentation/devicetree/bindings/phy/ti,tcan104x-can.yaml
+F: Documentation/networking/device_drivers/can/
F: drivers/net/can/
F: drivers/phy/phy-can-transceiver.c
F: include/linux/can/bittiming.h
@@ -19600,6 +19601,10 @@ F: samples/pktgen/
F: tools/net/
F: tools/testing/selftests/net/
X: Documentation/networking/batman-adv.rst
+X: Documentation/networking/can.rst
+X: Documentation/networking/device_drivers/can/
+X: Documentation/networking/iso15765-2.rst
+X: Documentation/networking/j1939.rst
X: Documentation/networking/mac80211-injection.rst
X: Documentation/networking/mac80211_hwsim/
X: Documentation/networking/regulatory.rst
---
base-commit: 79eb6679ef6a0d5ea68da53a8321fb1dc72299b9
change-id: 20261112-exclude-can-docs-from-netdev-56179ded5faf
Best regards,
--
Cunhao Lu <1579567540@qq.com>
reply other threads:[~2026-11-13 2:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20261113-exclude-can-docs-from-netdev-v2-1-8ae9dc553024@qq.com \
--to=devnull+1579567540.qq.com@kernel.org \
--cc=1579567540@qq.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mailhol@kernel.org \
--cc=max@enpas.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=pabeni@redhat.com \
--cc=robin@protonic.nl \
--cc=socketcan@hartkopp.net \
/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
all inboxes | Powered by JetHome®