From: Randy Dunlap <rdunlap@infradead.org>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Albert Ou <aou@eecs.berkeley.edu>,
Jonathan Corbet <corbet@lwn.net>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Paul Walmsley <pjw@kernel.org>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org, workflows@vger.kernel.org,
Alexandre Ghiti <alex@ghiti.fr>,
Shuah Khan <skhan@linuxfoundation.org>,
Dan Williams <djbw@kernel.org>
Subject: Re: [PATCH v2 00/11] Auto-generate maintainer profile entries
Date: Sat, 18 Apr 2026 17:05:56 -0700 [thread overview]
Message-ID: <9bcb8053-2eb6-4327-ae3f-2a23321c4c3e@infradead.org> (raw)
In-Reply-To: <cover.1776405189.git.mchehab+huawei@kernel.org>
On 4/16/26 11:11 PM, Mauro Carvalho Chehab wrote:
> Hi Jon,
>
> This patch series change the way maintainer entry profile links
> are added to the documentation. Instead of having an entry for
> each of them at an ReST file, get them from MAINTAINERS content.
>
> That should likely make easier to maintain, as there will be a single
> point to place all such profiles.
>
> The output is a per-subsystem sorted (*) series of links shown as a
> list like this:
>
> - Arm And Arm64 Soc Sub-Architectures (Common Parts)
> - Arm/Samsung S3C, S5P And Exynos Arm Architectures
> - Arm/Tesla Fsd Soc Support
> ...
> - Xfs Filesystem
>
> Please notice that the series is doing one logical change per patch.
> I could have merged some changes altogether, but I opted doing it
> in small steps to help reviews. If you prefer, feel free to merge
> maintainers_include changes on merge.
>
> There is one interesting side effect of this series: there is no
> need to add rst files containing profiles inside a TOC tree: Just
> creating the file anywhere inside Documentation and adding a P entry
> is enough. Adding them to a TOC won't hurt.
>
> Reported-by: Randy Dunlap <rdunlap@infradead.org>
> Suggested-by: Dan Williams <djbw@kernel.org>
> Closes: https://lore.kernel.org/linux-doc/69dd6299440be_147c801005b@djbw-dev.notmuch/
>
> (*) At the end, I opted to use sorted(), just to ensure it, even
> knowing that MAINTAINER entries are supposed to be sorted, as
> the cost of sorting ~20 already-sorted entries is negligible.
>
> ---
>
> v2:
> - I placed the to MAINTAINERS changes at the beginning.
> - fix a bug when O=DOCS is used;
> - proper handle glob "P" entries (just in case, no profiles use it ATM);
> - when SPHINXDIRS=process, instead of producing warnings, point to
> entries at https://docs.kernel.org;
> - MAINTAINERS parsing now happens just once;
> - The output won't be numered for entries inside numered TOC trees;
> - TOC tree is now hidden;
> - instead of display a TOC tree, it shows a list of profiles,
> ordered and named after file system name taken from MAINTAINERS file;
> - At the output list, both https and file profiles are shown the same
> way.
>
> Mauro Carvalho Chehab (11):
> MAINTAINERS: add an entry for media maintainers profile
> MAINTAINERS: add maintainer-tip.rst to X86
> docs: maintainers_include: auto-generate maintainer profile TOC
> docs: auto-generate maintainer entry profile links
> docs: maintainers_include: use a better title for profiles
> docs: maintainers_include: add external profile URLs
> docs: maintainers_include: preserve names for files under process/
> docs: maintainers_include: Only show main entry for profiles
> docs: maintainers_include: improve its output
> docs: maintainers_include: fix support for O=dir
> docs: maintainers_include: parse MAINTAINERS just once
>
> .../maintainer/maintainer-entry-profile.rst | 24 +--
> .../process/maintainer-handbooks.rst | 17 +-
> Documentation/sphinx/maintainers_include.py | 161 +++++++++++++++---
> MAINTAINERS | 2 +
> 4 files changed, 150 insertions(+), 54 deletions(-)
>
Just a note, not asking for a change or fix:
AFAICT, all P: entries are now listed nicely except for:
P: rust/pin-init/CONTRIBUTING.md
so for the series:
Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
Tested-by: Randy Dunlap <rdunlap@infradead.org>
thanks.
--
~Randy
next prev parent reply other threads:[~2026-04-19 0:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-17 6:11 [PATCH v2 00/11] Auto-generate maintainer profile entries Mauro Carvalho Chehab
2026-04-17 6:11 ` [PATCH v2 01/11] MAINTAINERS: add an entry for media maintainers profile Mauro Carvalho Chehab
2026-04-19 0:02 ` Randy Dunlap
2026-04-19 19:07 ` Mauro Carvalho Chehab
2026-04-17 6:11 ` [PATCH v2 02/11] MAINTAINERS: add maintainer-tip.rst to X86 Mauro Carvalho Chehab
2026-04-17 6:11 ` [PATCH v2 03/11] docs: maintainers_include: auto-generate maintainer profile TOC Mauro Carvalho Chehab
2026-04-17 6:11 ` [PATCH v2 04/11] docs: auto-generate maintainer entry profile links Mauro Carvalho Chehab
2026-04-17 6:11 ` [PATCH v2 05/11] docs: maintainers_include: use a better title for profiles Mauro Carvalho Chehab
2026-04-17 6:11 ` [PATCH v2 06/11] docs: maintainers_include: add external profile URLs Mauro Carvalho Chehab
2026-04-17 6:11 ` [PATCH v2 07/11] docs: maintainers_include: preserve names for files under process/ Mauro Carvalho Chehab
2026-04-17 6:11 ` [PATCH v2 08/11] docs: maintainers_include: Only show main entry for profiles Mauro Carvalho Chehab
2026-04-17 6:11 ` [PATCH v2 09/11] docs: maintainers_include: improve its output Mauro Carvalho Chehab
2026-04-17 6:11 ` [PATCH v2 10/11] docs: maintainers_include: fix support for O=dir Mauro Carvalho Chehab
2026-04-17 6:11 ` [PATCH v2 11/11] docs: maintainers_include: parse MAINTAINERS just once Mauro Carvalho Chehab
2026-04-19 0:05 ` Randy Dunlap [this message]
2026-04-19 19:04 ` [PATCH v2 00/11] 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=9bcb8053-2eb6-4327-ae3f-2a23321c4c3e@infradead.org \
--to=rdunlap@infradead.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=corbet@lwn.net \
--cc=djbw@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mchehab+huawei@kernel.org \
--cc=mchehab@kernel.org \
--cc=palmer@dabbelt.com \
--cc=pjw@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