workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.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>
Subject: Re: maintainer profiles
Date: Sat, 11 Apr 2026 17:02:56 -0700	[thread overview]
Message-ID: <a7421a41-458a-4925-a804-e31e2552c79e@infradead.org> (raw)
In-Reply-To: <d8804a85-dd2b-481e-903f-c6fea5d24c97@infradead.org>



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.
> 
> 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...

-- 
~Randy


  reply	other threads:[~2026-04-12  0:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-10  0:18 Randy Dunlap
2026-04-10  8:12 ` Mauro Carvalho Chehab
2026-04-11 23:54   ` Randy Dunlap
2026-04-12  0:02     ` Randy Dunlap [this message]
2026-04-12  6:31       ` Mauro Carvalho Chehab

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=a7421a41-458a-4925-a804-e31e2552c79e@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab+huawei@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox