From: Maxime Ripard <mripard@kernel.org>
To: Dave Stevenson <dave.stevenson@raspberrypi.com>
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>,
Daniel Vetter <daniel@ffwll.ch>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/2] MAINTAINERS: drm : vc4: Add Raspberry Pi as maintainers
Date: Fri, 21 Jun 2024 10:41:24 +0200 [thread overview]
Message-ID: <20240621-towering-fat-bug-2eea23@houat> (raw)
In-Reply-To: <CAPY8ntDLqTXvvpLb=6Q5TQD-Dzj1pScg_scUWBpcg3oBMggyxg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2069 bytes --]
On Thu, Jun 20, 2024 at 03:06:11PM GMT, Dave Stevenson wrote:
> On Thu, 20 Jun 2024 at 14:52, Maxime Ripard <mripard@kernel.org> wrote:
> >
> > On Thu, Jun 20, 2024 at 12:14:00PM GMT, Dave Stevenson wrote:
> > > Add myself and our kernel maintenance list as maintainers for
> > > VC4 alongside Maxime.
> > >
> > > Signed-off-by: Dave Stevenson <dave.stevenson@raspberrypi.com>
> > > ---
> > > MAINTAINERS | 2 ++
> > > 1 file changed, 2 insertions(+)
> > >
> > > diff --git a/MAINTAINERS b/MAINTAINERS
> > > index d1566c647a50..b6dd628d5bc6 100644
> > > --- a/MAINTAINERS
> > > +++ b/MAINTAINERS
> > > @@ -7520,6 +7520,8 @@ F: include/uapi/drm/v3d_drm.h
> > >
> > > DRM DRIVERS FOR VC4
> > > M: Maxime Ripard <mripard@kernel.org>
> > > +M: Dave Stevenson <dave.stevenson@raspberrypi.com>
> > > +M: Raspberry Pi Kernel Maintenance <kernel-list@raspberrypi.com>
> >
> > I don't think we can put a list as maintainer, maintainers (and
> > reviewers) should be explicit. We can definitely put the list as Cc with
> > L: though :)
>
> It's been accepted for Unicam
> https://github.com/torvalds/linux/blob/master/MAINTAINERS#L4178-L4183
I think it's somewhat different in the case of v4l2, you're the one
taking the patches and sending a PR iirc. In drm-misc, there's a
significant chance someone else will apply it.
> bcm-kernel-feedback-list@broadcom.com is listed as reviewer for a fair
> number of entries.
It's also a matter of signalling to the rest of the kernel community how
important a review is: if I get a review of someone on a patch that
isn't listed in MAINTAINERS, then it's valid but not enough for me to
merge it.
If it's from a reviewer, then it carries more weight, and if it's from a
maintainer, then it's pretty much the final word.
That only works if we explicitly put names in MAINTAINERS.
But I also don't care how many maintainers or reviewers you want to put
in MAINTAINERS, so it's not gatekeeping. It's mostly just around
documenting what the situation will be :)
Maxime
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2024-06-21 8:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-20 11:14 [PATCH 1/2] MAINTAINERS: drm : vc4: Add Raspberry Pi as maintainers Dave Stevenson
2024-06-20 11:14 ` [PATCH 2/2] MAINTAINERS: drm : vc4: Drop Emma's tree Dave Stevenson
2024-06-20 13:52 ` [PATCH 1/2] MAINTAINERS: drm : vc4: Add Raspberry Pi as maintainers Maxime Ripard
2024-06-20 14:06 ` Dave Stevenson
2024-06-21 8:41 ` Maxime Ripard [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=20240621-towering-fat-bug-2eea23@houat \
--to=mripard@kernel.org \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dave.stevenson@raspberrypi.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=tzimmermann@suse.de \
/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