From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id DCF1C3DFC68; Mon, 4 May 2026 15:51:28 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1777909888; cv=none; b=oKBWftuf6vmvjzAVA7kAZAoqpyIhSpJyjVsxWRo6OHpa6vu0djSd7sROpybo9Nbl2PDXB6wDXjLfiVwjq/gCryeB19ErmojmtBXKrtJ1/VQPOouojxyMyM/L+1ZCwPE0fXuFGocurXchQsgX2RXKiFBoAKrZsc356L4rDbUjdzM= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1777909888; c=relaxed/simple; bh=OziWK8aR/qkKZPas1bWViRZGxXO2Vk6TjcG6CgLnVIQ=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:Content-Type; b=vDIi0yh0TqcUGbhHogF2SN47FgjZZixb5PBClA4qCWEfZquOVIo5yWkkD6hcgpDxvo88ZccLEFnUkKU36XTGQ2WyZJQBqwWW252Y+y5jIzDNPABk9TJKE693hcYJlcTvaBkD2e1bTmCgh1xlMlnvlLXnB14TrMBGoQUO7IIE0Tw= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=jMNn0qDh; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="jMNn0qDh" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 7413DC2BCF5; Mon, 4 May 2026 15:51:28 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1777909888; bh=OziWK8aR/qkKZPas1bWViRZGxXO2Vk6TjcG6CgLnVIQ=; h=From:To:Cc:Subject:Date:From; b=jMNn0qDhbTtNj78mwBby2hTKZtXGCzY09CaHaaWJnG/gqjdSwUwZ20o+er7dXVwhX swcww/ryMg1QMGomOe2KRZK0u3fibx3A4m0PiCejl9gbbrdLsaQCPgAWWBzbAEjN8d iyMSIJpX6jL9PPmAPtY9EEsEMR7ZJnrqwl3r0wtoO9qXqo2UGif2yYqYp5ADTgJbp5 SVQj2bVrsSox8B1TFS/Q2tbVzRDSI9nLxkdXY5kkl1Iqiu6JEE98x1KR3LLzBUaqno aC9FSe2NUbSWRy1dLeZArzK3IJNrCkwuSpLtKxU10cmMwLDbJCEPmzNf/NY6txX462 cX8jAuwA69pbQ== Received: from mchehab by mail.kernel.org with local (Exim 4.99.1) (envelope-from ) id 1wJvZu-0000000Ey4N-1heV; Mon, 04 May 2026 17:51:26 +0200 From: Mauro Carvalho Chehab To: Jonathan Corbet , Mauro Carvalho Chehab , Miguel Ojeda Cc: Mauro Carvalho Chehab , linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org, =?UTF-8?q?Bj=C3=B6rn=20Roy=20Baron?= , Alice Ryhl , Andreas Hindborg , Andrew Morton , Benno Lossin , Boqun Feng , Danilo Krummrich , Gary Guo , Joe Perches , Matteo Croce , Shuah Khan , Trevor Gross Subject: [PATCH 0/9] Improve process/maintainers output Date: Mon, 4 May 2026 17:51:09 +0200 Message-ID: X-Mailer: git-send-email 2.54.0 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Sender: Mauro Carvalho Chehab Hi Jon, As promised, this series improve the output at process/maintainers: instead of a pure enriched text, the maintainer's file content is now converted with a table, and has gained a javascript to allow filtering entries. The initial patches change the logic to split parsing from output generation. Now, everything is stored into a dict at the parsing phase. This way, it is easier to adjust the directive handler for it to produce a more structured document. Right now, the entries are sorted alphabetically, per subsystem's name. --- As mentioned before, I did some extra tests here, changing the sort logic: - per mailing lists. Easy to do but require a couple of hints; - per number of files (after using iglob) to calculate the actual number of patches. This is fast with NVME, but could be slow with HDD. Doing that helps to group the output per subsytem (assuming that each major subsystem has its own mailing list), and placing the subsystem before each entry. Yet, after adding the JS filter, I'm not sure if it is worth doing it(*). So, I kept such changes out of the final version. In any case, with the new logic, changing the output is easy. (*) Hint: Try setting the box there to linux-doc :-D This one is sorted on a nice way, but if you set it to linux-media, you'll see that the first entry is Orphan. The most relevant one is hidden in the crowd. - It should also be easy to add some logic there at the Sphinx directive to allow, for instance, include per-subsystem entries, e.g. one could add, in the future, support for things like: .. maintainers-include:: mailing-list: linux-doc@vger.kernel.org sort-by: file-count And have a page inside the subsystem (Documentation on this example) with all maintainers per subsystem. This is just a rough idea. I'm currently not planning to implement it. Matteo Croce (1): docs: escape ** glob pattern in MAINTAINERS descriptions Mauro Carvalho Chehab (8): docs: maintainers_include: keep hidden TOC sorted docs: maintainers_include.py: split state machine on multiple funcs docs: maintainers_include: cleanup the code docs: maintainers_include.py: clean most SPHINXDIRS=process warnings docs: maintainers_include: do some coding style cleanups docs: maintainers_include: store maintainers entries on a dict docs: maintainers_include: don't ignore invalid profile entries docs: maintainers: add a filtering javascript Documentation/sphinx/maintainers_include.py | 405 ++++++++++++-------- 1 file changed, 249 insertions(+), 156 deletions(-) -- 2.54.0