On Mon, 4 May 2026 09:00:41 +0200 Mauro Carvalho Chehab <[email protected]> wrote:
> On Sun, 03 May 2026 09:49:41 -0600 > Jonathan Corbet <[email protected]> wrote: > > > Mauro Carvalho Chehab <[email protected]> writes: > > > > > Hi Jon, > > > > > > This is basically the same patch series I sent during the merge > > > window, rebased on the top of post 7.1-rc1 docs-next branch. > > > It is tested both with and without O=DOCS. > > > > > > It contains just one extra trivial patch adding a missing SPDX > > > header, and, on v4, I dropped two patches touching MAINTAINERS, > > > as those aren't needed anymore. > > > > > > 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. > > > > One thing I kind of dislike about these magic mechanisms is that we end > > up with a single, essentially unsorted list of stuff that readers have > > to go digging their way through. Heh, perhaps you're referring to the TOC tree. You'll see it unsorted on diffs because the TOC tree there is hidden. As it is a set, currently it will output a different result on each run. Not a problem for users, but it makes harder to check differences after patches, so I'm planning to submit a patch to keep it sorted just for the sake of doing: diff -u before/ after/ Thanks, Mauro
