Maintainer workflows discussions
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Jonathan Corbet <corbet@lwn.net>,
	Linux Doc Mailing List <linux-doc@vger.kernel.org>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
	workflows@vger.kernel.org,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Shuah Khan <skhan@linuxfoundation.org>,
	Randy Dunlap <rdunlap@infradead.org>
Subject: [PATCH v4 07/10] docs: maintainers_include: Only show main entry for profiles
Date: Mon, 27 Apr 2026 16:22:25 +0200	[thread overview]
Message-ID: <387b42c523e7b9f33e61cdff6fadb1df265cf71d.1777295258.git.mchehab+huawei@kernel.org> (raw)
In-Reply-To: <cover.1777295258.git.mchehab+huawei@kernel.org>

Instead of showing as a "Contents:" with 2 identation levels,
drop its title and show profiles as a list of entries.

Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
Tested-by: Randy Dunlap <rdunlap@infradead.org>
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
---
 Documentation/process/maintainer-handbooks.rst | 2 --
 Documentation/sphinx/maintainers_include.py    | 2 +-
 2 files changed, 1 insertion(+), 3 deletions(-)

diff --git a/Documentation/process/maintainer-handbooks.rst b/Documentation/process/maintainer-handbooks.rst
index 531985a0fae8..3821e78aefc0 100644
--- a/Documentation/process/maintainer-handbooks.rst
+++ b/Documentation/process/maintainer-handbooks.rst
@@ -16,6 +16,4 @@ For maintainers, consider documenting additional requirements and
 expectations if submissions routinely overlook specific submission
 criteria. See Documentation/maintainer/maintainer-entry-profile.rst.
 
-Contents:
-
 .. maintainers-profile-toc::
diff --git a/Documentation/sphinx/maintainers_include.py b/Documentation/sphinx/maintainers_include.py
index 948746b998a3..7ab921820612 100755
--- a/Documentation/sphinx/maintainers_include.py
+++ b/Documentation/sphinx/maintainers_include.py
@@ -235,7 +235,7 @@ class MaintainersProfile(Include):
         maint = MaintainersParser(base_path, path)
 
         output  = ".. toctree::\n"
-        output += "   :maxdepth: 2\n\n"
+        output += "   :maxdepth: 1\n\n"
 
         items = sorted(maint.profiles.items(),
                        key=lambda kv: (kv[1] or "", kv[0]))
-- 
2.53.0


  parent reply	other threads:[~2026-04-27 14:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-27 14:22 [PATCH v4 00/10] Auto-generate maintainer profile entries Mauro Carvalho Chehab
2026-04-27 14:22 ` [PATCH v4 01/10] docs: maintainers: add SPDX license to the file Mauro Carvalho Chehab
2026-04-27 14:22 ` [PATCH v4 02/10] docs: maintainers_include: auto-generate maintainer profile TOC Mauro Carvalho Chehab
2026-04-27 14:22 ` [PATCH v4 03/10] docs: auto-generate maintainer entry profile links Mauro Carvalho Chehab
2026-04-27 14:22 ` [PATCH v4 04/10] docs: maintainers_include: use a better title for profiles Mauro Carvalho Chehab
2026-04-27 14:22 ` [PATCH v4 05/10] docs: maintainers_include: add external profile URLs Mauro Carvalho Chehab
2026-04-27 14:22 ` [PATCH v4 06/10] docs: maintainers_include: preserve names for files under process/ Mauro Carvalho Chehab
2026-04-27 14:22 ` Mauro Carvalho Chehab [this message]
2026-04-27 14:22 ` [PATCH v4 08/10] docs: maintainers_include: improve its output Mauro Carvalho Chehab
2026-04-27 14:22 ` [PATCH v4 09/10] docs: maintainers_include: fix support for O=dir Mauro Carvalho Chehab
2026-04-27 14:22 ` [PATCH v4 10/10] docs: maintainers_include: parse MAINTAINERS just once Mauro Carvalho Chehab
2026-05-03 15:49 ` [PATCH v4 00/10] Auto-generate maintainer profile entries Jonathan Corbet
2026-05-04  7:00   ` Mauro Carvalho Chehab
2026-05-04 14:39     ` 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=387b42c523e7b9f33e61cdff6fadb1df265cf71d.1777295258.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=rdunlap@infradead.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