From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 1ECF2F9D0D2 for ; Tue, 14 Apr 2026 14:29:42 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:Message-ID:Date:Subject:Cc :To:From:Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References: List-Owner; bh=GhIupNe6Z0ji2uKgZwUJwVK4t/AmJoJbMNCcFJfu52c=; b=Mdue0kfvpucC2w HKES66Shd947jvamuQFRL7sAUOlMcZQFlDmqTgdbenD0qTxlB15T7HcRAcw9DLNgA7/ynd7NIMoyK 4eo0OoKJ4JGsbzRcv/P0mnZd5S3bltEArkb3cuMoBXGiC0Ijla6FD0BOCXhd8qnJXpzxgGKN1gC2s sY06r2my9ge/2WsjF+pIlPoO18nrgNiOKkPkRUOBeysNRyDNAiMVJuwZ5lszjuB/7j5UTZ4G5qa1y /dg4GYY+OxrIE/BWAUUOTotRjRctHNCGxfEF8NYIQQDp+dWkL+3N20DEU6a7L2TIpCARriSJBU3sY Iho1bXzpgmktnKrVeHDw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.98.2 #2 (Red Hat Linux)) id 1wCelW-0000000HSEK-3bTl; Tue, 14 Apr 2026 14:29:22 +0000 Received: from sea.source.kernel.org ([172.234.252.31]) by bombadil.infradead.org with esmtps (Exim 4.98.2 #2 (Red Hat Linux)) id 1wCelU-0000000HSCs-1iaj for linux-riscv@lists.infradead.org; Tue, 14 Apr 2026 14:29:21 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by sea.source.kernel.org (Postfix) with ESMTP id 5E28A417A9; Tue, 14 Apr 2026 14:29:19 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 34DB4C19425; Tue, 14 Apr 2026 14:29:19 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1776176959; bh=Q37AUFFWTils7bZ37skEl+Z0KEumAbKiDlGGPvgg1rU=; h=From:To:Cc:Subject:Date:From; b=JhP25WiPt9NmEuCKQqPRQVKvMhoCcERpHk8I/R3rO7z6IBni6WStoSNkTZ5CqdqTN cqjZPT8hNW4i0NkOToOuh3N359rqMi0jPufPNENeQUzvttBtl1wUtAkARATaq+9L6S 2UF85/QxjcxGGekPN1udtw94MZK78R28Wtzvk0f7BYMl27IIvbj3L+oVpgGAEQ0o+Z Sb8iWQfFoqGwBAQ2JxyE2bIcULny9v56815VgZ9PZTSsyLo1UvoIwK1hkGhzJjudLf YCgR4zMcpGfeUhf1P8Iqqdj3Tvz8AnwHgr+LQLkYWSOnSuyPswbla3klttdc9m/gHs bwNk1Y0nWoQhw== Received: from mchehab by mail.kernel.org with local (Exim 4.99.1) (envelope-from ) id 1wCelR-00000007oLK-0aJT; Tue, 14 Apr 2026 16:29:17 +0200 From: Mauro Carvalho Chehab To: Albert Ou , Jonathan Corbet , Dan Williams , Mauro Carvalho Chehab , Palmer Dabbelt , Paul Walmsley Cc: Mauro Carvalho Chehab , Randy Dunlap , linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org, workflows@vger.kernel.org, Alexandre Ghiti , Shuah Khan Subject: [PATCH RFC 0/4] Auto-generate maintainer profile entries Date: Tue, 14 Apr 2026 16:29:03 +0200 Message-ID: X-Mailer: git-send-email 2.52.0 MIME-Version: 1.0 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20260414_072920_490106_81E47E02 X-CRM114-Status: GOOD ( 15.23 ) X-BeenThere: linux-riscv@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-riscv" Errors-To: linux-riscv-bounces+linux-riscv=archiver.kernel.org@lists.infradead.org Hi Dan/Jon, This small 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. I made this as an RFC. The goal is mostly to be a start of discussions about how this is implemented. Also, it should be noticed that I'm not incorporating the diff content from Dan's sugggestion, as it was just an e-mail reply without a proper patch title/description/SoB. Some points on this RFC: 1. some P: entries are links to web pages. The current approach ignores them; 2. the current logic doesn't use glob. So, if one would add an entry like: P: Documentation/foo/profiles-*.rst it will generate an entry like "../foo/profiles-*". This probably works, as toc trees accept glob. 3. entries are placed at the order they occur at MAINTAINERS file (but duplication is properly handled); 4. as Randy mentioned, if an entry there is inside another TOC using numeration, those entries will have numeration as well; 5. the approach I took on patch 1 was a little bit lazy, as it ends processing MAINTAINERS two times, and there are some code duplication on different classes to handle path. I opted to do this way to minimize the differences, but it makes sense to clean the code later on newer versions of this series or after applying it; 6. patches 2 and 3 can be applied independently of this approach. They just add two missing "P:" entries to MAINTAINERS. Suggested-by: Dan Williams Closes: https://lore.kernel.org/linux-doc/69dd6299440be_147c801005b@djbw-dev.notmuch/ Mauro Carvalho Chehab (4): docs: maintainers_include: auto-generate maintainer profile TOC MAINTAINERS: add an entry for media maintainers profile MAINTAINERS: add maintainer-tip.rst to X86 docs: auto-generate maintainer entry profile links .../maintainer/maintainer-entry-profile.rst | 17 +--- .../process/maintainer-handbooks.rst | 10 +- Documentation/sphinx/maintainers_include.py | 93 +++++++++++++++---- MAINTAINERS | 2 + 4 files changed, 81 insertions(+), 41 deletions(-) -- 2.52.0 _______________________________________________ linux-riscv mailing list linux-riscv@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-riscv