public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Jacopo Mondi <jacopo.mondi@ideasonboard.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Nicolas Dufresne <nicolas.dufresne@collabora.com>,
	 Hans Verkuil <hverkuil+cisco@kernel.org>,
	linux-media@vger.kernel.org,
	 Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	Sakari Ailus <sakari.ailus@linux.intel.com>,
	 Sean Young <sean@mess.org>,
	Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
	 Ricardo Ribalda <ribalda@chromium.org>
Subject: Re: [PATCHv7 2/3] docs: media: document Media Maintainers
Date: Fri, 6 Feb 2026 09:30:19 +0100	[thread overview]
Message-ID: <aYWljU7ziHZ86lar@zed> (raw)
In-Reply-To: <20260205165912.GO156228@killaraus>

Hi Laurent

On Thu, Feb 05, 2026 at 06:59:12PM +0200, Laurent Pinchart wrote:
> On Thu, Feb 05, 2026 at 09:24:26AM -0500, Nicolas Dufresne wrote:
> > Le mardi 27 janvier 2026 à 11:53 +0100, Hans Verkuil a écrit :
> > > Document who the Media Maintainers are and what their
> > > responsibilities are.
> > >
> > > Signed-off-by: Hans Verkuil <hverkuil+cisco@kernel.org>
> > > ---
> > >  .../media/maintainer-entry-profile.rst        | 47 +++++++++++++++++--
> > >  1 file changed, 44 insertions(+), 3 deletions(-)
> > >
> > > diff --git a/Documentation/driver-api/media/maintainer-entry-profile.rst b/Documentation/driver-api/media/maintainer-entry-profile.rst
> > > index be4728b97759..4f73ee073860 100644
> > > --- a/Documentation/driver-api/media/maintainer-entry-profile.rst
> > > +++ b/Documentation/driver-api/media/maintainer-entry-profile.rst
> > > @@ -346,13 +346,54 @@ With the pull request workflow, pull requests shall use PGP-signed tags.
> > >  For more details about PGP signing, please read
> > >  Documentation/process/maintainer-pgp-guide.rst.
> > >  
> > > -Subsystem Media Maintainers
> > > ----------------------------
> > > +List of Media Maintainers
> > > +-------------------------
> > >  
> > > -The subsystem maintainers are:
> > > +The Media Maintainers listed here all have patchwork access and can
> > > +make Pull Requests or have commit rights.
> > > +
> > > +The Media Subsystem Maintainers are:
> > >    - Mauro Carvalho Chehab <mchehab@kernel.org>
> > >    - Hans Verkuil <hverkuil@kernel.org>
> > >  
> > > +The Media Core Maintainers are:
> > > +  - Sakari Ailus <sakari.ailus@linux.intel.com>
> > > +
> > > +    - ISP
> > > +    - sensor drivers
> > > +    - v4l2-async and v4l2-fwnode core frameworks
> > > +    - v4l2-flash-led-class core framework
> > > +
> > > +  - Mauro Carvalho Chehab <mchehab@kernel.org>
> > > +
> > > +    - DVB
> > > +
> > > +  - Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> > > +
> > > +    - Media controller drivers
> > > +    - Core media controller framework
>
> You could list me for ISPs as well, Sakari and I handle the together.
>
> I'm not alone there of course, it's a team effort and Dan and Jacopo are
> also active in developing and reviewing multiple ISP drivers. Not that
> we necessarily want to list them in this document (and I don't know if
> they would be interested), but I want publicly credit them in this mail
> for the work they do.
>

Thanks for pointing it out.

I have sent some pull request in the past and when it makes sense I
intend to do so for the drivers (or framework components) I take care
of.

As long as I can continue doing it, there's no need to list my name
here until we don't get to a model where more people can have commit
rights, which is still something I hope we can get to in a reasonable
time.

In any case, I'm certainly interested in partecipating in any effort
that could make the subsystem a little more agile.

Thanks
  j

> > > +
> > > +  - Hans Verkuil <hverkuil@kernel.org>
> > > +
> > > +    - V4L2 drivers
> > > +    - V4L2 and videobuf2 core frameworks
> > > +    - HDMI CEC drivers
> > > +    - HDMI CEC core framework
> > > +
> > > +  - Sean Young <sean@mess.org>
> > > +
> > > +    - Remote Controller (infrared) drivers
> > > +    - Remote Controller (infrared) core framework
> > > +
> > > +The Media Driver Maintainers responsible for specific areas are:
> > > +  - Nicolas Dufresne <nicolas.dufresne@collabora.com>
> > > +
> > > +    - Codec drivers
> >
> > I also took care of M2M color converters lately, while trying to delegate when
> > it makes sense (such as DWL100 delegated to Laurent). So we may (or may not)
> > add:
> >
> >        - M2M driver not otherwise delegated
> >
> > Reviewed-by: Nicolas Dufresne <nicolas.dufresne@collabora.com>
> >
> > > +
> > > +  - Bryan O'Donoghue <bryan.odonoghue@linaro.org>
> > > +
> > > +    - Qualcomm drivers
> > > +
> > >  Submit Checklist Addendum
> > >  -------------------------
> > >  
>
> --
> Regards,
>
> Laurent Pinchart
>

  reply	other threads:[~2026-02-06  8:30 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-27 10:53 [PATCHv7 0/3] docs: media: multicommitters model documentation Hans Verkuil
2026-01-27 10:53 ` [PATCHv7 1/3] docs: media: update maintainer-entry-profile for multi-committers Hans Verkuil
2026-02-05 11:37   ` Bryan O'Donoghue
2026-02-05 18:03   ` kernel test robot
2026-01-27 10:53 ` [PATCHv7 2/3] docs: media: document Media Maintainers Hans Verkuil
2026-02-05 11:38   ` Bryan O'Donoghue
2026-02-05 14:24   ` Nicolas Dufresne
2026-02-05 16:59     ` Laurent Pinchart
2026-02-06  8:30       ` Jacopo Mondi [this message]
2026-01-27 10:53 ` [PATCHv7 3/3] docs: media: document media multi-committers rules and process Hans Verkuil
2026-02-04 14:36 ` [PATCHv7 0/3] docs: media: multicommitters model documentation Mauro Carvalho Chehab
2026-02-04 14:37 ` [PATCH 1/2] docs: media: maintainer-entry-profile: do some editorial reviews Mauro Carvalho Chehab
2026-02-04 14:37   ` [PATCH 2/2] docs: media: media-committer: do some editorial changes Mauro Carvalho Chehab
2026-02-04 15:07     ` Mauro Carvalho Chehab
2026-02-05 11:52     ` Hans Verkuil
2026-02-05 13:51       ` Mauro Carvalho Chehab
2026-02-05 13:58         ` Hans Verkuil
2026-02-05 11:25   ` [PATCH 1/2] docs: media: maintainer-entry-profile: do some editorial reviews Hans Verkuil
2026-02-05 13:53     ` 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=aYWljU7ziHZ86lar@zed \
    --to=jacopo.mondi@ideasonboard.com \
    --cc=bryan.odonoghue@linaro.org \
    --cc=hverkuil+cisco@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox