All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Verkuil <hverkuil+cisco@kernel.org>
To: linux-media@vger.kernel.org
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	Sakari Ailus <sakari.ailus@linux.intel.com>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Sean Young <sean@mess.org>,
	Nicolas Dufresne <nicolas.dufresne@collabora.com>,
	Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
	Ricardo Ribalda <ribalda@chromium.org>
Subject: [PATCHv8 0/3] docs: media: multicommitters model documentation
Date: Thu,  5 Feb 2026 15:32:51 +0100	[thread overview]
Message-ID: <cover.1770301974.git.hverkuil+cisco@kernel.org> (raw)

Here is v8, based on Mauro's feedback.

The main changes since v7 are:

- rename media-committer.rst to media-committers.rst
- the 'Note' at the start of media-committers.rst is now just a list
  of additional responsibilies (it made no sense that it was a 'Note').
- incorporated Mauro's suggestions

Patch 1/3 updates maintainer-entry-profile.rst: it introduces the
three Media maintainer levels (Media Driver Maintainer, Media Core Maintainer
and Media Subsystem Maintainer) and what the responsibilities are.

Patch 2/3 adds back and updates the list of Media Maintainers that
disappeared in patch 1/3. Please verify this whether the email
addresses are the correct ones, and verify that the areas of responsibility
are correct and that nothing is missing.

Patch 3/3 adds media-committers.rst: that focusses on the additional
commit rights that can be granted to a Media Maintainer.

I have uploaded the documentation with these patches here:

https://hverkuil.home.xs4all.nl/spec/driver-api/maintainer-entry-profile.html
https://hverkuil.home.xs4all.nl/spec/driver-api/media-committers.html

Mauro's feedback for v7 is here:

https://patchwork.linuxtv.org/project/linux-media/list/?series=21550

Regards,

	Hans

Hans Verkuil (1):
  docs: media: document Media Maintainers

Mauro Carvalho Chehab (2):
  docs: media: update maintainer-entry-profile for multi-committers
  docs: media: document media multi-committers rules and process

 Documentation/driver-api/media/index.rst      |   1 +
 .../media/maintainer-entry-profile.rst        | 451 +++++++++++++++---
 .../driver-api/media/media-committers.rst     | 201 ++++++++
 3 files changed, 591 insertions(+), 62 deletions(-)
 create mode 100644 Documentation/driver-api/media/media-committers.rst

-- 
2.51.0


             reply	other threads:[~2026-02-05 14:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-05 14:32 Hans Verkuil [this message]
2026-02-05 14:32 ` [PATCHv8 1/3] docs: media: update maintainer-entry-profile for multi-committers Hans Verkuil
2026-02-05 14:32 ` [PATCHv8 2/3] docs: media: document Media Maintainers Hans Verkuil
2026-02-05 14:32 ` [PATCHv8 3/3] docs: media: document media multi-committers rules and process Hans Verkuil
2026-02-05 15:58 ` [PATCHv8 0/3] docs: media: multicommitters model documentation Mauro Carvalho Chehab
2026-02-05 15:58   ` Mauro Carvalho Chehab
2026-02-06 17:09 ` Sakari Ailus

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.1770301974.git.hverkuil+cisco@kernel.org \
    --to=hverkuil+cisco@kernel.org \
    --cc=bryan.odonoghue@linaro.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab+huawei@kernel.org \
    --cc=nicolas.dufresne@collabora.com \
    --cc=ribalda@chromium.org \
    --cc=sakari.ailus@linux.intel.com \
    --cc=sean@mess.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.