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>
Subject: Re: maintainer profiles
Date: Fri, 10 Apr 2026 10:12:39 +0200 [thread overview]
Message-ID: <20260410101239.04c87f26@foz.lan> (raw)
In-Reply-To: <b7775383-da94-4098-8af9-2f672c4f1a71@infradead.org>
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.
Thanks,
Mauro
next prev parent reply other threads:[~2026-04-10 8:12 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 [this message]
2026-04-11 23:54 ` Randy Dunlap
2026-04-12 0:02 ` Randy Dunlap
2026-04-12 6:31 ` Mauro Carvalho Chehab
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=20260410101239.04c87f26@foz.lan \
--to=mchehab+huawei@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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.