public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Hans Verkuil <hverkuil+cisco@kernel.org>
Cc: linux-media@vger.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: Re: [PATCHv9 0/3] docs: media: multicommitters model documentation
Date: Wed, 11 Feb 2026 11:55:52 +0100	[thread overview]
Message-ID: <20260211115552.4241695f@localhost> (raw)
In-Reply-To: <cover.1770800320.git.hverkuil+cisco@kernel.org>

On Wed, 11 Feb 2026 09:58:37 +0100
Hans Verkuil <hverkuil+cisco@kernel.org> wrote:

> The main changes since v8 are:
> 
> - Typo/grammar fixes from Mauro
> - Added additional maintainer areas for Laurent and Sakari (patch 2/3)
> - Additional links to git development trees
> 
> 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

Heh, every time I read I find minor issues, but at this point, I guess
this version does the job. So, let's stick with it.


> 
> 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        | 461 +++++++++++++++---
>  .../driver-api/media/media-committers.rst     | 201 ++++++++
>  3 files changed, 601 insertions(+), 62 deletions(-)
>  create mode 100644 Documentation/driver-api/media/media-committers.rst
> 


-- 
Thanks,
Mauro

      parent reply	other threads:[~2026-02-11 10:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-11  8:58 [PATCHv9 0/3] docs: media: multicommitters model documentation Hans Verkuil
2026-02-11  8:58 ` [PATCHv9 1/3] docs: media: update maintainer-entry-profile for multi-committers Hans Verkuil
2026-02-11  8:58 ` [PATCHv9 2/3] docs: media: document Media Maintainers Hans Verkuil
2026-02-11  8:58 ` [PATCHv9 3/3] docs: media: document media multi-committers rules and process Hans Verkuil
2026-02-11 10:55 ` Mauro Carvalho Chehab [this message]

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=20260211115552.4241695f@localhost \
    --to=mchehab+huawei@kernel.org \
    --cc=bryan.odonoghue@linaro.org \
    --cc=hverkuil+cisco@kernel.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox