From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Jonathan Corbet <corbet@lwn.net>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
workflows@vger.kernel.org, Shuah Khan <skhan@linuxfoundation.org>
Subject: [PATCH v3 08/12] docs: maintainers_include: preserve names for files under process/
Date: Mon, 27 Apr 2026 15:00:08 +0200 [thread overview]
Message-ID: <44165bb12641055e4ecadb2ba95fde36fb46ff86.1777294623.git.mchehab+huawei@kernel.org> (raw)
In-Reply-To: <cover.1777294623.git.mchehab+huawei@kernel.org>
When a maintainer's profile is stored outside process, they're
already included on some other book and the name of the filesystem
may not be there. That's why the logic picks the name from the
subsystem's name.
However, files directly placed together with maintainers-handbooks.rst
(e.g. under Documentation/process/) is a different history: those
aren't placed anywhere, so we can keep using their own names,
letting Sphinx do his thing.
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
---
Documentation/sphinx/maintainers_include.py | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/Documentation/sphinx/maintainers_include.py b/Documentation/sphinx/maintainers_include.py
index f1b8d4b00c2a..948746b998a3 100755
--- a/Documentation/sphinx/maintainers_include.py
+++ b/Documentation/sphinx/maintainers_include.py
@@ -76,11 +76,13 @@ class MaintainersParser:
match = re.match(r"P:\s*(Documentation/\S+)\.rst", line)
if match:
fname = os.path.relpath(match.group(1), base_path)
- if fname not in self.profiles:
+ if fname.startswith("../"):
if self.profiles.get(fname) is None:
self.profiles[fname] = subsystem_name
else:
self.profiles[fname] += f", {subsystem_name}"
+ else:
+ self.profiles[fname] = None
match = re.match(r"P:\s*(https?://.*)", line)
if match:
--
2.53.0
next prev parent reply other threads:[~2026-04-27 13:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-27 13:00 [PATCH v3 00/12] Auto-generate maintainer profile entries Mauro Carvalho Chehab
2026-04-27 13:00 ` [PATCH v3 01/12] MAINTAINERS: add an entry for media maintainers profile Mauro Carvalho Chehab
2026-04-27 13:00 ` [PATCH v3 02/12] MAINTAINERS: add maintainer-tip.rst to X86 Mauro Carvalho Chehab
2026-04-27 13:00 ` [PATCH v3 03/12] docs: maintainers: add SPDX license to the file Mauro Carvalho Chehab
2026-04-27 13:00 ` [PATCH v3 04/12] docs: maintainers_include: auto-generate maintainer profile TOC Mauro Carvalho Chehab
2026-04-27 13:00 ` [PATCH v3 05/12] docs: auto-generate maintainer entry profile links Mauro Carvalho Chehab
2026-04-27 13:00 ` [PATCH v3 06/12] docs: maintainers_include: use a better title for profiles Mauro Carvalho Chehab
2026-04-27 13:00 ` [PATCH v3 07/12] docs: maintainers_include: add external profile URLs Mauro Carvalho Chehab
2026-04-27 13:00 ` Mauro Carvalho Chehab [this message]
2026-04-27 13:00 ` [PATCH v3 09/12] docs: maintainers_include: Only show main entry for profiles Mauro Carvalho Chehab
2026-04-27 13:00 ` [PATCH v3 10/12] docs: maintainers_include: improve its output Mauro Carvalho Chehab
2026-04-27 13:00 ` [PATCH v3 11/12] docs: maintainers_include: fix support for O=dir Mauro Carvalho Chehab
2026-04-27 13:00 ` [PATCH v3 12/12] docs: maintainers_include: parse MAINTAINERS just once Mauro Carvalho Chehab
2026-04-27 13:05 ` [PATCH v3 00/12] Auto-generate maintainer profile entries Mauro Carvalho Chehab
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=44165bb12641055e4ecadb2ba95fde36fb46ff86.1777294623.git.mchehab+huawei@kernel.org \
--to=mchehab+huawei@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mchehab@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=workflows@vger.kernel.org \
/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