Re: maintainer profiles

[Mauro Carvalho Chehab <mchehab+huawei@kernel.org>]

On Sat, 11 Apr 2026 16:54:00 -0700
Randy Dunlap <rdunlap@infradead.org> wrote:

> Also, does anyone know why some of these profiles are numbered and some
> are not?  See
>   https://docs.kernel.org/maintainer/maintainer-entry-profile.html#existing-profiles
> for odd numbering.

Patch 9/8 fixes it, while solving other issues:

- https://lore.kernel.org/linux-doc/cfff2b313d1f79a5919f400020a1b1a4064a7143.1776252056.git.mchehab+huawei@kernel.org/T/#u

Basically, it creates a hidden TOC which is not displayed, creating
this ReST output:

	- :doc:`Arm And Arm64 Soc Sub-Architectures (Common Parts) <maintainer-soc>`
	- :doc:`Arm/Samsung S3C, S5P And Exynos Arm Architectures <maintainer-soc-clean-dts>`
	- :doc:`Arm/Tesla Fsd Soc Support <maintainer-soc-clean-dts>`
	- `Audit Subsystem <https://github.com/linux-audit/audit-kernel/blob/main/README.md>`_
	- :doc:`Damon <../mm/damon/maintainer-profile>`
	- :doc:`Documentation <../doc-guide/maintainer-profile>`
	- :doc:`Google Tensor Soc Support <maintainer-soc-clean-dts>`
	- :doc:`Kernel Nfsd, Sunrpc, And Lockd Servers <../filesystems/nfs/nfsd-maintainer-entry-profile>`
	- :doc:`Kernel Virtual Machine For X86 (Kvm/X86) <maintainer-kvm-x86>`
	- :doc:`Libnvdimm Btt: Block Translation Table <../nvdimm/maintainer-entry-profile>`
	- :doc:`Libnvdimm Pmem: Persistent Memory Driver <../nvdimm/maintainer-entry-profile>`
	- :doc:`Libnvdimm: Non-Volatile Memory Device Subsystem <../nvdimm/maintainer-entry-profile>`
	- :doc:`Media Input Infrastructure (V4L/Dvb) <../driver-api/media/maintainer-entry-profile>`
	- :doc:`Networking Drivers <maintainer-netdev>`
	- :doc:`Networking [General] <maintainer-netdev>`
	- :doc:`Risc-V Architecture <../arch/riscv/patch-acceptance>`
	- `Rust <https://rust-for-linux.com/contributing>`_
	- `Security Subsystem <https://github.com/LinuxSecurityModule/kernel/blob/main/README.md>`_
	- `Selinux Security Module <https://github.com/SELinuxProject/selinux-kernel/blob/main/README.md>`_
	- :doc:`Vfio Pci Device Specific Drivers <../driver-api/vfio-pci-device-specific-driver-acceptance>`
	- :doc:`X86 Architecture (32-Bit And 64-Bit) <maintainer-tip>`
	- :doc:`Xfs Filesystem <../filesystems/xfs/xfs-maintainer-entry-profile>`

	.. toctree::
	   :hidden:

	   ../filesystems/xfs/xfs-maintainer-entry-profile
	   ../driver-api/vfio-pci-device-specific-driver-acceptance
	   maintainer-netdev
	   ../nvdimm/maintainer-entry-profile
	   maintainer-soc
	   maintainer-soc-clean-dts
	   ../doc-guide/maintainer-profile
	   maintainer-kvm-x86
	   ../mm/damon/maintainer-profile
	   ../driver-api/media/maintainer-entry-profile
	   ../arch/riscv/patch-acceptance
	   ../filesystems/nfs/nfsd-maintainer-entry-profile
	   maintainer-tip

E.g. instead of showing the contents of the TOC tree, it shows a
per-subsystem sorted list of items. The TOC tree is used there just
to avoid warnings that a .rst file is not placed on a TOC.

The advantage of such approach is that there's now one item at
the list for each "P:" tag at MAINTAINERS. All of them are
displayed using the name of the subsystem as described there,
e.g. it outputs:

     • Arm And Arm64 Soc Sub-Architectures (Common Parts)
     • Arm/Samsung S3C, S5P And Exynos Arm Architectures
     • Arm/Tesla Fsd Soc Support
     • Audit Subsystem
     • Damon
     • Documentation
     • Google Tensor Soc Support
     • Kernel Nfsd, Sunrpc, And Lockd Servers
     • Kernel Virtual Machine For X86 (Kvm/X86)
     • Libnvdimm Btt: Block Translation Table
     • Libnvdimm Pmem: Persistent Memory Driver
     • Libnvdimm: Non-Volatile Memory Device Subsystem
     • Media Input Infrastructure (V4L/Dvb)
     • Networking Drivers
     • Networking [General]
     • Risc-V Architecture
     • Rust
     • Security Subsystem
     • Selinux Security Module
     • Vfio Pci Device Specific Drivers
     • X86 Architecture (32-Bit And 64-Bit)
     • Xfs Filesystem

Each of entry there with either a cross-reference to a document or
with a reference to an external site.

Thanks,
Mauro