From: Manuel Ebner <manuelebner@mailbox.org>
To: Jonathan Corbet <corbet@lwn.net>, Shuah Khan <skhan@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
workflows@vger.kernel.org
Subject: [Issue] maintainer-handbooks: html: list has duplicates
Date: Sun, 12 Jul 2026 12:45:53 +0200 [thread overview]
Message-ID: <98a558a87a07ab641f47c66c372ee7ed0735f4f5.camel@mailbox.org> (raw)
Hi,
I was reading documentation when I stumbled across this. There's a lot of
repetition in the list at: https://docs.kernel.org/process/maintainer-handbooks.html
See below.
Thanks
Manuel
> [...]
> For maintainers, consider documenting additional requirements and expectations if submissions
> routinely overlook specific submission criteria. See Maintainer Entry Profile.
>
> process/maintainer-soc
> process/maintainer-soc-clean-dts
> process/maintainer-soc-clean-dts
> Audit Subsystem
> process/maintainer-tip
> process/maintainer-tip
> mm/damon/maintainer-profile
> process/maintainer-tip
> doc-guide/maintainer-profile
> process/maintainer-tip
> process/maintainer-tip
> process/maintainer-soc-clean-dts
> process/maintainer-tip
> process/maintainer-tip
> process/maintainer-tip
> filesystems/nfs/nfsd-maintainer-entry-profile
> process/maintainer-kvm-x86
> nvdimm/maintainer-entry-profile
> nvdimm/maintainer-entry-profile
> nvdimm/maintainer-entry-profile
> process/maintainer-tip
> driver-api/media/maintainer-entry-profile
> process/maintainer-netdev
> process/maintainer-netdev
> process/maintainer-tip
> process/maintainer-tip
> process/maintainer-tip
> process/maintainer-tip
> arch/riscv/patch-acceptance
> Rust
> Rust [Pin-Init]
> process/maintainer-tip
> Security Subsystem
> Selinux Security Module
> driver-api/vfio-pci-device-specific-driver-acceptance
> process/maintainer-tip
> filesystems/xfs/xfs-maintainer-entry-profile
next reply other threads:[~2026-07-12 10:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-12 10:45 Manuel Ebner [this message]
2026-07-12 11:56 ` Manuel Ebner
2026-07-12 11:58 ` Manuel Ebner
2026-07-12 14:39 ` 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=98a558a87a07ab641f47c66c372ee7ed0735f4f5.camel@mailbox.org \
--to=manuelebner@mailbox.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=skhan@linuxfoundation.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