From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from ms.lwn.net (ms.lwn.net [45.79.88.28]) (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 CE04E37D108; Sun, 3 May 2026 15:49:45 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=45.79.88.28 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1777823386; cv=none; b=GdHczF/NkgMuJ1olxqRLR6LXKcqi23wkDZgQQLo4GYS7a95wgRg3kGV1wHe3u9o9IJMD/Aowms+Dyw7mfY6phsnXsU2qWUCLKSisxY+ghHwmJakAUH99DFV91J0S8QW2UPfge9nCsDMkKXEX5a1uXwIgZN04z/keC9hHBpzdHs4= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1777823386; c=relaxed/simple; bh=RDxXyby5jaTtmik7CmFLeKp/NnpDI0QYF//KGQkZcP0=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=JE+WXKhhv62aYmv8/qskIS0MBHyGLYaw43QRkUpndkLC64InXo6B+ptoyfthwA2S9wLF83Z/VmnSKy/+PyWUleyMMaZ0Tsm5/kHuKYSq/h4S+wJeEq2PKXXrT0iIKqM971+fLt+oEZ39WyKbswgg9dSn/ymgRh43pUcsgAaJSOc= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=lwn.net; spf=pass smtp.mailfrom=lwn.net; dkim=pass (2048-bit key) header.d=lwn.net header.i=@lwn.net header.b=XzNZnuWO; arc=none smtp.client-ip=45.79.88.28 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=lwn.net Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=lwn.net Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=lwn.net header.i=@lwn.net header.b="XzNZnuWO" DKIM-Filter: OpenDKIM Filter v2.11.0 ms.lwn.net 79A9541084 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lwn.net; s=20201203; t=1777823385; bh=eUBtAkliWo7i/sWVQgdPYh5z/4C4V+lwPevehSBP+nY=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=XzNZnuWOaLrDGZPmdknv8VRbuHLT3VllHLzEnVWBPAk9UORi8sVvmJ3b+pFgJdn36 reK7NjyFWnX5GRYo6Pf9lBFBdSXzzrl6flyBP/5xMWWUo1/yLlJqRYulIV6jiB53ue Cw4H3KQkuTw4QZbOVm1KMrjRDvVoSW60ZZdMpUlC8esU8JfT1+QzjA4BrsaiyRutHI rOwAFZp44GoZifu/HtcWATteUeQU7VhxEOVxD0+lq5F93AkLt0FyGAwHz4xVMCGwKz +2ZODrVjLQXSHcB/mFL6C0vNIVR4Q36uoKTaD4wSWn/m2GnpmiNRaPXcLrmtDgajUc RNPkAbo0iteYw== Received: from localhost (mdns.lwn.net [45.79.72.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (prime256v1) server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by ms.lwn.net (Postfix) with ESMTPSA id 79A9541084; Sun, 3 May 2026 15:49:44 +0000 (UTC) From: Jonathan Corbet To: Mauro Carvalho Chehab , Albert Ou , Mauro Carvalho Chehab , Palmer Dabbelt , Paul Walmsley Cc: Mauro Carvalho Chehab , linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org, workflows@vger.kernel.org, Alexandre Ghiti , Shuah Khan , Randy Dunlap , Dan Williams Subject: Re: [PATCH v4 00/10] Auto-generate maintainer profile entries In-Reply-To: References: Date: Sun, 03 May 2026 09:49:41 -0600 Message-ID: <87lde0bii2.fsf@trenco.lwn.net> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain Mauro Carvalho Chehab 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. It would be nice if we could somehow apply a bit of structure; as the number of these handbooks grows, our readers would appreciate it. Oh well, one can always hope. Meanwhile, this seems useful, I've applied it. Thanks, jon