public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Sakari Ailus <sakari.ailus@iki.fi>
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 3/3] docs: media: profile: make it clearer about maintainership duties
Date: Tue, 3 Dec 2024 10:28:46 +0100	[thread overview]
Message-ID: <20241203102846.6fb3ab52@foz.lan> (raw)
In-Reply-To: <Z03I1R0aRylSz742@valkosipuli.retiisi.eu>

Em Mon, 2 Dec 2024 14:48:53 +0000
Sakari Ailus <sakari.ailus@iki.fi> escreveu:

> Hi Mauro,
> 
> On Mon, Dec 02, 2024 at 10:26:21AM +0100, Mauro Carvalho Chehab wrote:
> > During the review of the media committes profile, it was noticed  
> 
> s/committe\K/r/

Addressed this and the other editorial changes.

> Can we expect people listed as maintainers to either send PRs or be media
> committers? I think this might be eventually the result but I think we're
> quite far from this currently and I expect things to remain that way in the
> near future.

Yes, having driver maintainers being committers and sending PRs is what we
expect to happen first.

For mid/long-term, once driver maintainers get in board, we may also have
other committers for the drivers whose maintainer is also a committer.

Now, having committers for drivers whose maintainer is not a committer
doesn't sound a good idea, except if such committer is doing just
janitorial work and gets A-B/R-B from the driver maintainer on all
patches he merges.

Thanks,
Mauro

  reply	other threads:[~2024-12-03  9:28 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-02  9:26 [PATCH v3 0/3] Document the new media-committer's model Mauro Carvalho Chehab
2024-12-02  9:26 ` [PATCH v3 1/3] docs: media: update maintainer-entry-profile for multi-committers Mauro Carvalho Chehab
2024-12-02 12:40   ` Sakari Ailus
2024-12-02 13:23     ` Mauro Carvalho Chehab
2024-12-03 11:52       ` Sakari Ailus
2024-12-02 13:17   ` Hans Verkuil
2024-12-02 13:54     ` Mauro Carvalho Chehab
2024-12-02 14:49       ` Hans Verkuil
2024-12-02 20:48       ` Ricardo Ribalda
2024-12-02  9:26 ` [PATCH v3 2/3] docs: media: document media multi-committers rules and process Mauro Carvalho Chehab
2024-12-02 14:13   ` Sakari Ailus
2024-12-03  8:26     ` Mauro Carvalho Chehab
2024-12-03 10:03       ` Sakari Ailus
2024-12-02 14:37   ` Hans Verkuil
2024-12-02  9:26 ` [PATCH v3 3/3] docs: media: profile: make it clearer about maintainership duties Mauro Carvalho Chehab
2024-12-02 14:40   ` Hans Verkuil
2024-12-02 14:48   ` Sakari Ailus
2024-12-03  9:28     ` Mauro Carvalho Chehab [this message]
2024-12-03 12:49       ` Sakari Ailus
2024-12-02 15:03 ` [PATCH v3 0/3] Document the new media-committer's model Hans Verkuil
2024-12-03  7:19   ` Mauro Carvalho Chehab
2024-12-03 11:22     ` Laurent Pinchart
2024-12-03 13:07       ` Mauro Carvalho Chehab
2024-12-09  8:15         ` Media committers model postponed to 6.14 - Was: " Mauro Carvalho Chehab
2025-02-07 11:54           ` Hans Verkuil
2025-02-10  7:00             ` 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=20241203102846.6fb3ab52@foz.lan \
    --to=mchehab+huawei@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=sakari.ailus@iki.fi \
    /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