All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Linux Documentation <linux-doc@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Jonathan Corbet <corbet@lwn.net>,
	Linux Kernel Workflows <workflows@vger.kernel.org>,
	Dan Williams <dan.j.williams@intel.com>,
	Thomas Gleixner <tglx@kernel.org>
Subject: Re: maintainer profiles
Date: Sun, 12 Apr 2026 08:31:14 +0200	[thread overview]
Message-ID: <20260412083114.3cadb4d5@foz.lan> (raw)
In-Reply-To: <a7421a41-458a-4925-a804-e31e2552c79e@infradead.org>

On Sat, 11 Apr 2026 17:02:56 -0700
Randy Dunlap <rdunlap@infradead.org> wrote:

> On 4/11/26 4:54 PM, Randy Dunlap wrote:
> > Hi,
> > 
> > On 4/10/26 1:12 AM, Mauro Carvalho Chehab wrote:  
> >> On Thu, 9 Apr 2026 17:18:39 -0700
> >> Randy Dunlap <rdunlap@infradead.org> wrote:
> >>  
> >>> Hi,
> >>>
> >>> Is there supposed to be a difference (or distinction) in the contents of
> >>>
> >>> Documentation/process/maintainer-handbooks.rst
> >>> and
> >>> Documentation/maintainer/maintainer-entry-profile.rst
> >>> ?
> >>>
> >>> Can they be combined into one location?  
> >>
> >> Heh, from the 5 entries at maintainer-handbooks.rst:
> >>
> >>    maintainer-netdev
> >>    maintainer-soc
> >>    maintainer-soc-clean-dts
> >>    maintainer-tip
> >>    maintainer-kvm-x86
> >>
> >> we have 3 of them already there at maintainer-entry-profile.rst:
> >>
> >>    $ grep process/ Documentation/maintainer/maintainer-entry-profile.rst
> >>    ../process/maintainer-soc
> >>    ../process/maintainer-soc-clean-dts
> >>    ../process/maintainer-netdev
> >>
> >> It sounds to me that moving maintainer-tip and maintainer-kvm-x86
> >> to maintainer-entry-profile.rst would be enough to drop
> >> maintainer-handbooks.rst, keeping them consolidated on a single
> >> place.  
> > 
> > Yes, maybe. How about in the other direction:
> > move them all to maintainer-handbooks.rst?
> > 
> > After all, maintainer-entry-profile.rst says:
> >   For now, existing maintainer profiles are listed here; we will likely want
> >   to do something different in the near future.

(added Don and Thomas to the thread)

I don't have strong preferences, but the maintainer-entry-profile.rst
contains a "default" maintainership model, so, whatever file name,
I would preserve at least most of its contents somewhere.

Probably a more important discussions is where they should would
sit:

- at Documentation/process;
- at Documentation/maintainer;

Another option would be to move the contents from/two those two
books.

> > 
> > 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.  
> 
> Because they are numbered in their own respective documentation areas...
> 

Yes: they're actually links to other places:

 .. toctree::
   :maxdepth: 1

   ../doc-guide/maintainer-profile
   ../nvdimm/maintainer-entry-profile
   ../arch/riscv/patch-acceptance
   ../process/maintainer-soc
   ../process/maintainer-soc-clean-dts
   ../driver-api/media/maintainer-entry-profile
   ../process/maintainer-netdev
   ../driver-api/vfio-pci-device-specific-driver-acceptance
   ../nvme/feature-and-quirk-policy
   ../filesystems/nfs/nfsd-maintainer-entry-profile
   ../filesystems/xfs/xfs-maintainer-entry-profile
   ../mm/damon/maintainer-profile

On most cases, the profile is located together with other
subsystem-specific docs, as it makes easier to maintain there,
together with other documents from a given subsystem.

It also saves the need to add extra entries at MAINTAINERS
file.

Thanks,
Mauro

  reply	other threads:[~2026-04-12  6:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-10  0:18 maintainer profiles Randy Dunlap
2026-04-10  8:12 ` Mauro Carvalho Chehab
2026-04-11 23:54   ` Randy Dunlap
2026-04-12  0:02     ` Randy Dunlap
2026-04-12  6:31       ` Mauro Carvalho Chehab [this message]
2026-04-15 11:43     ` Mauro Carvalho Chehab
2026-04-13 19:03 ` Jonathan Corbet
2026-04-13 21:39   ` Dan Williams
2026-04-13 23:08     ` Randy Dunlap
2026-04-14 12:37     ` Mauro Carvalho Chehab
2026-04-14 14:32       ` Mauro Carvalho Chehab
2026-04-15  0:44         ` Dan Williams
2026-04-14 11:18 ` Krzysztof Kozlowski
2026-04-15  2:03   ` Randy Dunlap

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260412083114.3cadb4d5@foz.lan \
    --to=mchehab+huawei@kernel.org \
    --cc=corbet@lwn.net \
    --cc=dan.j.williams@intel.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=tglx@kernel.org \
    --cc=workflows@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.