From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: Hans de Goede <hdegoede@redhat.com>,
Hans Verkuil <hverkuil@xs4all.nl>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-media@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: Add Hans de Goede as USB VIDEO CLASS co-maintainer
Date: Tue, 19 Nov 2024 09:20:02 +0200 [thread overview]
Message-ID: <20241119072002.GN12409@pendragon.ideasonboard.com> (raw)
In-Reply-To: <20241118071801.51894f08@foz.lan>
Hi Mauro,
On Mon, Nov 18, 2024 at 07:18:01AM +0100, Mauro Carvalho Chehab wrote:
> Em Sun, 17 Nov 2024 23:38:37 +0200 Laurent Pinchart escreveu:
> > On Sat, Nov 16, 2024 at 12:38:55PM +0100, Hans de Goede wrote:
> > > Add myself as co-maintainer for the UVC driver.
> >
> > Thanks for volunteering to help.
> >
> > > Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> > > Signed-off-by: Hans de Goede <hdegoede@redhat.com>
> >
> > Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> >
> > > ---
> > > MAINTAINERS | 1 +
> > > 1 file changed, 1 insertion(+)
> > >
> > > diff --git a/MAINTAINERS b/MAINTAINERS
> > > index 91d0609db61b..1da403e89159 100644
> > > --- a/MAINTAINERS
> > > +++ b/MAINTAINERS
> > > @@ -24063,6 +24063,7 @@ F: drivers/usb/host/uhci*
> > >
> > > USB VIDEO CLASS
> > > M: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> > > +M: Hans de Goede <hdegoede@redhat.com>
> > > L: linux-media@vger.kernel.org
> > > S: Maintained
> > > W: http://www.ideasonboard.org/uvc/
> >
> > I think we should update the git tree entry as well, as we're using
> > https://gitlab.freedesktop.org/linux-media/users/uvc/. As that's
> > temporary until we can merge patches directly in the multi-committers
> > tree, it may however not be worth it. What do you think ?
>
> The official tree is now at:
>
> git://linuxtv.org/media.git
>
> Such tree is not expected to be rebased, so IMO the best is to point
> to it. I just submitted a patch mass-updating the references to
> media_tree.git to it. Such patch has to be backported, as even
> stable versions should be pointing to an existing tree (and we may
> soon get rid of the media_tree.git and media_stage.git trees).
>
> Assuming that we have a smooth process, I don't expect that patches
> at the uvc merge tree to be there for a long time. Also, this is
> meant to be a short-lived tree with the migration to media-committers
> (which is a tree that can be rebased).
>
> So, IMO, it is not worth pointing to the uvc merge tree.
The migration to the multi-committers tree is the main reason why I
don't think it's worth it to point to
https://gitlab.freedesktop.org/linux-media/users/uvc/, assuming we start
using the multi-committers model very soon. Once done, the git tree
entry should point to that tree.
--
Regards,
Laurent Pinchart
prev parent reply other threads:[~2024-11-19 7:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-16 11:38 [PATCH] MAINTAINERS: Add Hans de Goede as USB VIDEO CLASS co-maintainer Hans de Goede
2024-11-17 21:38 ` Laurent Pinchart
2024-11-18 6:02 ` Mauro Carvalho Chehab
2024-11-18 6:18 ` Mauro Carvalho Chehab
2024-11-19 7:20 ` Laurent Pinchart [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=20241119072002.GN12409@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=hdegoede@redhat.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=mchehab@kernel.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