From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org, workflows@vger.kernel.org
Subject: [PATCH v5 0/5] multicommiters model documentation
Date: Fri, 22 Aug 2025 10:33:40 +0200 [thread overview]
Message-ID: <cover.1755851331.git.mchehab+huawei@kernel.org> (raw)
This is a respin over the latest discussions with regards to the media
multicommitters model.
Feel free to reply with tecnical comments to the text, but personal
attacks and CoC violations won't be tolerated this time.
Mauro Carvalho Chehab (5):
docs: maintainer-pgp-guide.rst: add a reference for kernel.org sign
MAINTAINERS: fix a couple issues at media input infrastructure
docs: media: update maintainer-entry-profile for multi-committers
docs: media: document media multi-committers rules and process
docs: media: profile: make it clearer about maintainership duties
Documentation/driver-api/media/index.rst | 1 +
.../media/maintainer-entry-profile.rst | 256 ++++++++++++----
.../driver-api/media/media-committer.rst | 280 ++++++++++++++++++
.../process/maintainer-pgp-guide.rst | 2 +
MAINTAINERS | 3 +-
5 files changed, 490 insertions(+), 52 deletions(-)
create mode 100644 Documentation/driver-api/media/media-committer.rst
--
2.50.1
next reply other threads:[~2025-08-22 8:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-22 8:33 Mauro Carvalho Chehab [this message]
2025-08-22 8:33 ` [PATCH v5 1/5] docs: maintainer-pgp-guide.rst: add a reference for kernel.org sign Mauro Carvalho Chehab
-- strict thread matches above, loose matches on Subject: below --
2025-09-02 10:02 [PATCH v5 0/5] multicommiters model documentation 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=cover.1755851331.git.mchehab+huawei@kernel.org \
--to=mchehab+huawei@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.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;
as well as URLs for NNTP newsgroup(s).