* Re: drm-misc migration to Gitlab server
2024-02-20 8:49 drm-misc migration to Gitlab server Maxime Ripard
@ 2024-02-20 9:04 ` Maxime Ripard
2024-02-20 11:25 ` Daniel Stone
2024-02-26 11:33 ` Jani Nikula
` (6 subsequent siblings)
7 siblings, 1 reply; 32+ messages in thread
From: Maxime Ripard @ 2024-02-20 9:04 UTC (permalink / raw)
To: dri-devel
Cc: Daniel Vetter, David Airlie, Maarten Lankhorst, Thomas Zimmermann,
Daniel Stone
[-- Attachment #1: Type: text/plain, Size: 1114 bytes --]
On Tue, Feb 20, 2024 at 09:49:25AM +0100, Maxime Ripard wrote:
> Hi,
>
> As you might have noticed in your mails, Daniel Stone and I have been
> working on adding all the drm-misc maintainers and committers to Gitlab.
>
> The current repository was still in the cgit instance and was creating
> an unnecessary burden on the admins.
>
> For example, any new user had to create an issue and go through Daniel
> to create an cgit account, even though that user already needed to have
> a gitlab account to create the issue in the first place. Adding an SSH
> key was a similar story. By moving to Gitlab, we'll remove most of that
> burden.
>
> This will be mostly transparent to current committers and users: we'll
> still use dim, in the exact same way, the only change will be the URL of
> the repo. This will also be transparent to linux-next, since the
> linux-next branch lives in its own repo and is pushed by dim when
> pushing a branch.
Actually, I double-checked and linux-next pulls our branches directly,
so once the transition is over we'll have to notify them too.
Maxime
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
^ permalink raw reply [flat|nested] 32+ messages in thread* Re: drm-misc migration to Gitlab server
2024-02-20 9:04 ` Maxime Ripard
@ 2024-02-20 11:25 ` Daniel Stone
2024-02-20 22:46 ` Stephen Rothwell
0 siblings, 1 reply; 32+ messages in thread
From: Daniel Stone @ 2024-02-20 11:25 UTC (permalink / raw)
To: Maxime Ripard
Cc: dri-devel, Daniel Vetter, David Airlie, Maarten Lankhorst,
Thomas Zimmermann, Daniel Stone, Stephen Rothwell
On Tue, 20 Feb 2024 at 09:05, Maxime Ripard <mripard@kernel.org> wrote:
> On Tue, Feb 20, 2024 at 09:49:25AM +0100, Maxime Ripard wrote:
> > This will be mostly transparent to current committers and users: we'll
> > still use dim, in the exact same way, the only change will be the URL of
> > the repo. This will also be transparent to linux-next, since the
> > linux-next branch lives in its own repo and is pushed by dim when
> > pushing a branch.
>
> Actually, I double-checked and linux-next pulls our branches directly,
> so once the transition is over we'll have to notify them too.
cc sfr - once we move the DRM repos to a different location, what's
the best way to update linux-next?
That being said, we could set up read-only pull mirrors in the old
location ... something I want to do in March (because what else are
you going to do on holiday?) is to kill the write repos on kemper
(git.fd.o), move them to being on molly (cgit/anongit.fd.o) only, and
just have a cronjob that regularly pulls from all the gl.fd.o repos,
rather than pushing from GitLab.
Cheers,
Daniel
^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: drm-misc migration to Gitlab server
2024-02-20 11:25 ` Daniel Stone
@ 2024-02-20 22:46 ` Stephen Rothwell
2024-02-21 0:22 ` Daniel Stone
` (3 more replies)
0 siblings, 4 replies; 32+ messages in thread
From: Stephen Rothwell @ 2024-02-20 22:46 UTC (permalink / raw)
To: Daniel Stone
Cc: Maxime Ripard, dri-devel, Daniel Vetter, David Airlie,
Maarten Lankhorst, Thomas Zimmermann, Daniel Stone
[-- Attachment #1: Type: text/plain, Size: 2169 bytes --]
Hi Daniel,
On Tue, 20 Feb 2024 11:25:05 +0000 Daniel Stone <daniel@fooishbar.org> wrote:
>
> On Tue, 20 Feb 2024 at 09:05, Maxime Ripard <mripard@kernel.org> wrote:
> > On Tue, Feb 20, 2024 at 09:49:25AM +0100, Maxime Ripard wrote:
> > > This will be mostly transparent to current committers and users: we'll
> > > still use dim, in the exact same way, the only change will be the URL of
> > > the repo. This will also be transparent to linux-next, since the
> > > linux-next branch lives in its own repo and is pushed by dim when
> > > pushing a branch.
> >
> > Actually, I double-checked and linux-next pulls our branches directly,
> > so once the transition is over we'll have to notify them too.
>
> cc sfr - once we move the DRM repos to a different location, what's
> the best way to update linux-next?
>
> That being said, we could set up read-only pull mirrors in the old
> location ... something I want to do in March (because what else are
> you going to do on holiday?) is to kill the write repos on kemper
> (git.fd.o), move them to being on molly (cgit/anongit.fd.o) only, and
> just have a cronjob that regularly pulls from all the gl.fd.o repos,
> rather than pushing from GitLab.
These are (I think) all the drm trees/branches that I fetch every day:
git://anongit.freedesktop.org/drm-intel#for-linux-next
git://anongit.freedesktop.org/drm-intel#for-linux-next-fixes
git://anongit.freedesktop.org/drm/drm-misc#for-linux-next
git://anongit.freedesktop.org/drm/drm-misc#for-linux-next-fixes
git://git.freedesktop.org/git/drm/drm.git#drm-fixes
git://git.freedesktop.org/git/drm/drm.git#drm-next
git://git.freedesktop.org/git/drm/drm.git#topic/drm-ci
git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos.git#for-linux-next
https://gitlab.freedesktop.org/agd5f/linux#drm-next
https://gitlab.freedesktop.org/drm/msm.git#msm-next
https://gitlab.freedesktop.org/drm/tegra.git#for-next
https://gitlab.freedesktop.org/lumag/msm.git#msm-next-lumag
If someone could just send me all the new equivalent URLs when the
change happens, I will fix them up in my config.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 32+ messages in thread* Re: drm-misc migration to Gitlab server
2024-02-20 22:46 ` Stephen Rothwell
@ 2024-02-21 0:22 ` Daniel Stone
2024-02-26 14:50 ` Daniel Vetter
` (2 subsequent siblings)
3 siblings, 0 replies; 32+ messages in thread
From: Daniel Stone @ 2024-02-21 0:22 UTC (permalink / raw)
To: Stephen Rothwell
Cc: Maxime Ripard, dri-devel, Daniel Vetter, David Airlie,
Maarten Lankhorst, Thomas Zimmermann, Daniel Stone
Hi Stephen,
On Tue, 20 Feb 2024 at 22:46, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> On Tue, 20 Feb 2024 11:25:05 +0000 Daniel Stone <daniel@fooishbar.org> wrote:
> > cc sfr - once we move the DRM repos to a different location, what's
> > the best way to update linux-next?
>
> These are (I think) all the drm trees/branches that I fetch every day:
>
> [...]
>
> If someone could just send me all the new equivalent URLs when the
> change happens, I will fix them up in my config.
Thanks a lot! We'll give you a shout with a couple of days' heads-up
before we move then.
Cheers,
Daniel
^ permalink raw reply [flat|nested] 32+ messages in thread* Re: drm-misc migration to Gitlab server
2024-02-20 22:46 ` Stephen Rothwell
2024-02-21 0:22 ` Daniel Stone
@ 2024-02-26 14:50 ` Daniel Vetter
2024-02-26 21:35 ` Stephen Rothwell
2024-02-28 16:33 ` Daniel Vetter
2024-03-14 8:39 ` Maxime Ripard
3 siblings, 1 reply; 32+ messages in thread
From: Daniel Vetter @ 2024-02-26 14:50 UTC (permalink / raw)
To: Stephen Rothwell
Cc: Daniel Stone, Maxime Ripard, dri-devel, Daniel Vetter,
David Airlie, Maarten Lankhorst, Thomas Zimmermann, Daniel Stone
On Wed, Feb 21, 2024 at 09:46:43AM +1100, Stephen Rothwell wrote:
> Hi Daniel,
>
> On Tue, 20 Feb 2024 11:25:05 +0000 Daniel Stone <daniel@fooishbar.org> wrote:
> >
> > On Tue, 20 Feb 2024 at 09:05, Maxime Ripard <mripard@kernel.org> wrote:
> > > On Tue, Feb 20, 2024 at 09:49:25AM +0100, Maxime Ripard wrote:
> > > > This will be mostly transparent to current committers and users: we'll
> > > > still use dim, in the exact same way, the only change will be the URL of
> > > > the repo. This will also be transparent to linux-next, since the
> > > > linux-next branch lives in its own repo and is pushed by dim when
> > > > pushing a branch.
> > >
> > > Actually, I double-checked and linux-next pulls our branches directly,
> > > so once the transition is over we'll have to notify them too.
> >
> > cc sfr - once we move the DRM repos to a different location, what's
> > the best way to update linux-next?
> >
> > That being said, we could set up read-only pull mirrors in the old
> > location ... something I want to do in March (because what else are
> > you going to do on holiday?) is to kill the write repos on kemper
> > (git.fd.o), move them to being on molly (cgit/anongit.fd.o) only, and
> > just have a cronjob that regularly pulls from all the gl.fd.o repos,
> > rather than pushing from GitLab.
>
> These are (I think) all the drm trees/branches that I fetch every day:
>
> git://anongit.freedesktop.org/drm-intel#for-linux-next
> git://anongit.freedesktop.org/drm-intel#for-linux-next-fixes
> git://anongit.freedesktop.org/drm/drm-misc#for-linux-next
> git://anongit.freedesktop.org/drm/drm-misc#for-linux-next-fixes
> git://git.freedesktop.org/git/drm/drm.git#drm-fixes
> git://git.freedesktop.org/git/drm/drm.git#drm-next
> git://git.freedesktop.org/git/drm/drm.git#topic/drm-ci
This one you can drop right away, it's all merged, apologies for not
telling you earlier.
-Sima
> git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos.git#for-linux-next
> https://gitlab.freedesktop.org/agd5f/linux#drm-next
> https://gitlab.freedesktop.org/drm/msm.git#msm-next
> https://gitlab.freedesktop.org/drm/tegra.git#for-next
> https://gitlab.freedesktop.org/lumag/msm.git#msm-next-lumag
>
> If someone could just send me all the new equivalent URLs when the
> change happens, I will fix them up in my config.
>
> --
> Cheers,
> Stephen Rothwell
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: drm-misc migration to Gitlab server
2024-02-26 14:50 ` Daniel Vetter
@ 2024-02-26 21:35 ` Stephen Rothwell
0 siblings, 0 replies; 32+ messages in thread
From: Stephen Rothwell @ 2024-02-26 21:35 UTC (permalink / raw)
To: Daniel Vetter
Cc: Daniel Stone, Maxime Ripard, dri-devel, David Airlie,
Maarten Lankhorst, Thomas Zimmermann, Daniel Stone
[-- Attachment #1: Type: text/plain, Size: 312 bytes --]
Hi Daniel,
On Mon, 26 Feb 2024 15:50:10 +0100 Daniel Vetter <daniel@ffwll.ch> wrote:
>
> > git://git.freedesktop.org/git/drm/drm.git#topic/drm-ci
>
> This one you can drop right away, it's all merged, apologies for not
> telling you earlier.
Thanks, removed now.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: drm-misc migration to Gitlab server
2024-02-20 22:46 ` Stephen Rothwell
2024-02-21 0:22 ` Daniel Stone
2024-02-26 14:50 ` Daniel Vetter
@ 2024-02-28 16:33 ` Daniel Vetter
2024-02-28 21:56 ` Stephen Rothwell
2024-03-14 8:39 ` Maxime Ripard
3 siblings, 1 reply; 32+ messages in thread
From: Daniel Vetter @ 2024-02-28 16:33 UTC (permalink / raw)
To: Stephen Rothwell
Cc: Daniel Stone, Maxime Ripard, dri-devel, Daniel Vetter,
David Airlie, Maarten Lankhorst, Thomas Zimmermann, Daniel Stone
Hi Stephen!
On Wed, Feb 21, 2024 at 09:46:43AM +1100, Stephen Rothwell wrote:
> On Tue, 20 Feb 2024 11:25:05 +0000 Daniel Stone <daniel@fooishbar.org> wrote:
> >
> > On Tue, 20 Feb 2024 at 09:05, Maxime Ripard <mripard@kernel.org> wrote:
> > > On Tue, Feb 20, 2024 at 09:49:25AM +0100, Maxime Ripard wrote:
> > > > This will be mostly transparent to current committers and users: we'll
> > > > still use dim, in the exact same way, the only change will be the URL of
> > > > the repo. This will also be transparent to linux-next, since the
> > > > linux-next branch lives in its own repo and is pushed by dim when
> > > > pushing a branch.
> > >
> > > Actually, I double-checked and linux-next pulls our branches directly,
> > > so once the transition is over we'll have to notify them too.
> >
> > cc sfr - once we move the DRM repos to a different location, what's
> > the best way to update linux-next?
> >
> > That being said, we could set up read-only pull mirrors in the old
> > location ... something I want to do in March (because what else are
> > you going to do on holiday?) is to kill the write repos on kemper
> > (git.fd.o), move them to being on molly (cgit/anongit.fd.o) only, and
> > just have a cronjob that regularly pulls from all the gl.fd.o repos,
> > rather than pushing from GitLab.
>
> These are (I think) all the drm trees/branches that I fetch every day:
>
> git://anongit.freedesktop.org/drm-intel#for-linux-next
> git://anongit.freedesktop.org/drm-intel#for-linux-next-fixes
> git://anongit.freedesktop.org/drm/drm-misc#for-linux-next
> git://anongit.freedesktop.org/drm/drm-misc#for-linux-next-fixes
> git://git.freedesktop.org/git/drm/drm.git#drm-fixes
> git://git.freedesktop.org/git/drm/drm.git#drm-next
To test out the process we've moved drm.git first. It's now here:
https://gitlab.freedesktop.org/drm/kernel.git
Still the same two branches. Can you please update the url? We haven't
enabled the auto-mirror for this one, since we want to make sure the
upgrade path in the tooling works and people do switch over to the new
repo.
For the others the plan is keep the old places automatically mirrored, at
least until the dust has settled.
Thanks!
> git://git.freedesktop.org/git/drm/drm.git#topic/drm-ci
> git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos.git#for-linux-next
> https://gitlab.freedesktop.org/agd5f/linux#drm-next
> https://gitlab.freedesktop.org/drm/msm.git#msm-next
> https://gitlab.freedesktop.org/drm/tegra.git#for-next
> https://gitlab.freedesktop.org/lumag/msm.git#msm-next-lumag
>
> If someone could just send me all the new equivalent URLs when the
> change happens, I will fix them up in my config.
>
> --
> Cheers,
> Stephen Rothwell
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: drm-misc migration to Gitlab server
2024-02-28 16:33 ` Daniel Vetter
@ 2024-02-28 21:56 ` Stephen Rothwell
0 siblings, 0 replies; 32+ messages in thread
From: Stephen Rothwell @ 2024-02-28 21:56 UTC (permalink / raw)
To: Daniel Vetter
Cc: Daniel Stone, Maxime Ripard, dri-devel, David Airlie,
Maarten Lankhorst, Thomas Zimmermann, Daniel Stone
[-- Attachment #1: Type: text/plain, Size: 632 bytes --]
Hi Daniel,
On Wed, 28 Feb 2024 17:33:28 +0100 Daniel Vetter <daniel@ffwll.ch> wrote:
>
> > git://git.freedesktop.org/git/drm/drm.git#drm-fixes
> > git://git.freedesktop.org/git/drm/drm.git#drm-next
>
> To test out the process we've moved drm.git first. It's now here:
>
> https://gitlab.freedesktop.org/drm/kernel.git
>
> Still the same two branches. Can you please update the url? We haven't
> enabled the auto-mirror for this one, since we want to make sure the
> upgrade path in the tooling works and people do switch over to the new
> repo.
Done. They seem to be fine.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: drm-misc migration to Gitlab server
2024-02-20 22:46 ` Stephen Rothwell
` (2 preceding siblings ...)
2024-02-28 16:33 ` Daniel Vetter
@ 2024-03-14 8:39 ` Maxime Ripard
2024-03-14 10:00 ` Stephen Rothwell
3 siblings, 1 reply; 32+ messages in thread
From: Maxime Ripard @ 2024-03-14 8:39 UTC (permalink / raw)
To: Stephen Rothwell
Cc: Daniel Stone, dri-devel, Daniel Vetter, David Airlie,
Maarten Lankhorst, Thomas Zimmermann, Daniel Stone
[-- Attachment #1: Type: text/plain, Size: 1826 bytes --]
Hi Stephen,
On Wed, Feb 21, 2024 at 09:46:43AM +1100, Stephen Rothwell wrote:
> Hi Daniel,
>
> On Tue, 20 Feb 2024 11:25:05 +0000 Daniel Stone <daniel@fooishbar.org> wrote:
> >
> > On Tue, 20 Feb 2024 at 09:05, Maxime Ripard <mripard@kernel.org> wrote:
> > > On Tue, Feb 20, 2024 at 09:49:25AM +0100, Maxime Ripard wrote:
> > > > This will be mostly transparent to current committers and users: we'll
> > > > still use dim, in the exact same way, the only change will be the URL of
> > > > the repo. This will also be transparent to linux-next, since the
> > > > linux-next branch lives in its own repo and is pushed by dim when
> > > > pushing a branch.
> > >
> > > Actually, I double-checked and linux-next pulls our branches directly,
> > > so once the transition is over we'll have to notify them too.
> >
> > cc sfr - once we move the DRM repos to a different location, what's
> > the best way to update linux-next?
> >
> > That being said, we could set up read-only pull mirrors in the old
> > location ... something I want to do in March (because what else are
> > you going to do on holiday?) is to kill the write repos on kemper
> > (git.fd.o), move them to being on molly (cgit/anongit.fd.o) only, and
> > just have a cronjob that regularly pulls from all the gl.fd.o repos,
> > rather than pushing from GitLab.
>
> These are (I think) all the drm trees/branches that I fetch every day:
>
> git://anongit.freedesktop.org/drm-intel#for-linux-next
> git://anongit.freedesktop.org/drm-intel#for-linux-next-fixes
> git://anongit.freedesktop.org/drm/drm-misc#for-linux-next
> git://anongit.freedesktop.org/drm/drm-misc#for-linux-next-fixes
We've migrated the drm-misc repo to:
https://gitlab.freedesktop.org/drm/misc/kernel.git
The branch names are the same
Maxime
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
^ permalink raw reply [flat|nested] 32+ messages in thread* Re: drm-misc migration to Gitlab server
2024-03-14 8:39 ` Maxime Ripard
@ 2024-03-14 10:00 ` Stephen Rothwell
0 siblings, 0 replies; 32+ messages in thread
From: Stephen Rothwell @ 2024-03-14 10:00 UTC (permalink / raw)
To: Maxime Ripard
Cc: Daniel Stone, dri-devel, Daniel Vetter, David Airlie,
Maarten Lankhorst, Thomas Zimmermann, Daniel Stone
[-- Attachment #1: Type: text/plain, Size: 325 bytes --]
Hi Maxime,
On Thu, 14 Mar 2024 09:39:24 +0100 Maxime Ripard <mripard@kernel.org> wrote:
>
> We've migrated the drm-misc repo to:
> https://gitlab.freedesktop.org/drm/misc/kernel.git
>
> The branch names are the same
I have switched over for tomorrow and test fetches work fine.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: drm-misc migration to Gitlab server
2024-02-20 8:49 drm-misc migration to Gitlab server Maxime Ripard
2024-02-20 9:04 ` Maxime Ripard
@ 2024-02-26 11:33 ` Jani Nikula
2024-02-26 11:41 ` Maxime Ripard
2024-02-26 11:36 ` [dim PATCH] dim: drm-misc: Membership requests now go through Gitlab Maxime Ripard
` (5 subsequent siblings)
7 siblings, 1 reply; 32+ messages in thread
From: Jani Nikula @ 2024-02-26 11:33 UTC (permalink / raw)
To: Maxime Ripard, dri-devel
Cc: Daniel Vetter, David Airlie, Maarten Lankhorst, Thomas Zimmermann,
Daniel Stone
On Tue, 20 Feb 2024, Maxime Ripard <mripard@kernel.org> wrote:
> ## Adding the a remaining users
>
> I was able to identify most of the users with an account on the old git
> server. However, there's a few I couldn't match with certainty to a
> gitlab account:
>
> * andr2000
> * jsarha
>
> Please let me know your Gitlab user so I can add them to the group.
Is there no way for project owners/maintainers to see the email
addresses for members or access requests?
We've been pretty lax with giving reporter role to deal with issues, but
it's quite a different thing to give developer role with push access,
and feels like you'll need a side channel to match usernames with email
addresses.
BR,
Jani.
--
Jani Nikula, Intel
^ permalink raw reply [flat|nested] 32+ messages in thread* Re: drm-misc migration to Gitlab server
2024-02-26 11:33 ` Jani Nikula
@ 2024-02-26 11:41 ` Maxime Ripard
2024-02-26 11:57 ` Jani Nikula
0 siblings, 1 reply; 32+ messages in thread
From: Maxime Ripard @ 2024-02-26 11:41 UTC (permalink / raw)
To: Jani Nikula
Cc: dri-devel, Daniel Vetter, David Airlie, Maarten Lankhorst,
Thomas Zimmermann, Daniel Stone
[-- Attachment #1: Type: text/plain, Size: 1421 bytes --]
On Mon, Feb 26, 2024 at 01:33:24PM +0200, Jani Nikula wrote:
> On Tue, 20 Feb 2024, Maxime Ripard <mripard@kernel.org> wrote:
> > ## Adding the a remaining users
> >
> > I was able to identify most of the users with an account on the old git
> > server. However, there's a few I couldn't match with certainty to a
> > gitlab account:
> >
> > * andr2000
> > * jsarha
> >
> > Please let me know your Gitlab user so I can add them to the group.
>
> Is there no way for project owners/maintainers to see the email
> addresses for members or access requests?
>
> We've been pretty lax with giving reporter role to deal with issues, but
> it's quite a different thing to give developer role with push access,
> and feels like you'll need a side channel to match usernames with email
> addresses.
For the recent-ish subscriptions, it's possible since we've required to
open a Gitlab issue for a while, so we have the association between the
Gitlab account and the SSH account already.
During the Gitlab setup, the groups were also created already with the
people that had an SSH account at the time, and Gitlab account.
But for the rest, yeah, I had to ping Daniel S. about it. He could find
a few matches, but there's some where we just don't know if or what the
Gitlab account is.
Generally speaking, we've been conservative about it, and only added
accounts we were sure of.
Maxime
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: drm-misc migration to Gitlab server
2024-02-26 11:41 ` Maxime Ripard
@ 2024-02-26 11:57 ` Jani Nikula
2024-02-26 12:00 ` Daniel Stone
0 siblings, 1 reply; 32+ messages in thread
From: Jani Nikula @ 2024-02-26 11:57 UTC (permalink / raw)
To: Maxime Ripard
Cc: dri-devel, Daniel Vetter, David Airlie, Maarten Lankhorst,
Thomas Zimmermann, Daniel Stone
On Mon, 26 Feb 2024, Maxime Ripard <mripard@kernel.org> wrote:
> On Mon, Feb 26, 2024 at 01:33:24PM +0200, Jani Nikula wrote:
>> On Tue, 20 Feb 2024, Maxime Ripard <mripard@kernel.org> wrote:
>> > ## Adding the a remaining users
>> >
>> > I was able to identify most of the users with an account on the old git
>> > server. However, there's a few I couldn't match with certainty to a
>> > gitlab account:
>> >
>> > * andr2000
>> > * jsarha
>> >
>> > Please let me know your Gitlab user so I can add them to the group.
>>
>> Is there no way for project owners/maintainers to see the email
>> addresses for members or access requests?
>>
>> We've been pretty lax with giving reporter role to deal with issues, but
>> it's quite a different thing to give developer role with push access,
>> and feels like you'll need a side channel to match usernames with email
>> addresses.
>
> For the recent-ish subscriptions, it's possible since we've required to
> open a Gitlab issue for a while, so we have the association between the
> Gitlab account and the SSH account already.
>
> During the Gitlab setup, the groups were also created already with the
> people that had an SSH account at the time, and Gitlab account.
>
> But for the rest, yeah, I had to ping Daniel S. about it. He could find
> a few matches, but there's some where we just don't know if or what the
> Gitlab account is.
>
> Generally speaking, we've been conservative about it, and only added
> accounts we were sure of.
Ah, I didn't make myself clear. I'm more interested in the process going
forward, for new access requests. Anyone can create an account and
request access; how does a maintainer verify the request? For our
purposes it's basically just matching againt the email addresses in
existing commits in the repo.
BR,
Jani.
--
Jani Nikula, Intel
^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: drm-misc migration to Gitlab server
2024-02-26 11:57 ` Jani Nikula
@ 2024-02-26 12:00 ` Daniel Stone
2024-02-26 12:03 ` Jani Nikula
2024-02-26 13:14 ` Maxime Ripard
0 siblings, 2 replies; 32+ messages in thread
From: Daniel Stone @ 2024-02-26 12:00 UTC (permalink / raw)
To: Jani Nikula
Cc: Maxime Ripard, dri-devel, Daniel Vetter, David Airlie,
Maarten Lankhorst, Thomas Zimmermann, Daniel Stone
On Mon, 26 Feb 2024 at 11:57, Jani Nikula <jani.nikula@linux.intel.com> wrote:
> On Mon, 26 Feb 2024, Maxime Ripard <mripard@kernel.org> wrote:
> > For the recent-ish subscriptions, it's possible since we've required to
> > open a Gitlab issue for a while, so we have the association between the
> > Gitlab account and the SSH account already.
> >
> > During the Gitlab setup, the groups were also created already with the
> > people that had an SSH account at the time, and Gitlab account.
> >
> > But for the rest, yeah, I had to ping Daniel S. about it. He could find
> > a few matches, but there's some where we just don't know if or what the
> > Gitlab account is.
> >
> > Generally speaking, we've been conservative about it, and only added
> > accounts we were sure of.
>
> Ah, I didn't make myself clear. I'm more interested in the process going
> forward, for new access requests. Anyone can create an account and
> request access; how does a maintainer verify the request? For our
> purposes it's basically just matching againt the email addresses in
> existing commits in the repo.
It's a fair question. If you want to verify that someone is
@intel.com, maybe get them to email you out-of-band to check it. If
you want to check something else, just ask an admin I suppose.
Cheers,
Daniel
^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: drm-misc migration to Gitlab server
2024-02-26 12:00 ` Daniel Stone
@ 2024-02-26 12:03 ` Jani Nikula
2024-02-26 12:09 ` Daniel Stone
2024-02-26 13:14 ` Maxime Ripard
1 sibling, 1 reply; 32+ messages in thread
From: Jani Nikula @ 2024-02-26 12:03 UTC (permalink / raw)
To: Daniel Stone
Cc: Maxime Ripard, dri-devel, Daniel Vetter, David Airlie,
Maarten Lankhorst, Thomas Zimmermann, Daniel Stone
On Mon, 26 Feb 2024, Daniel Stone <daniel@fooishbar.org> wrote:
> On Mon, 26 Feb 2024 at 11:57, Jani Nikula <jani.nikula@linux.intel.com> wrote:
>> On Mon, 26 Feb 2024, Maxime Ripard <mripard@kernel.org> wrote:
>> > For the recent-ish subscriptions, it's possible since we've required to
>> > open a Gitlab issue for a while, so we have the association between the
>> > Gitlab account and the SSH account already.
>> >
>> > During the Gitlab setup, the groups were also created already with the
>> > people that had an SSH account at the time, and Gitlab account.
>> >
>> > But for the rest, yeah, I had to ping Daniel S. about it. He could find
>> > a few matches, but there's some where we just don't know if or what the
>> > Gitlab account is.
>> >
>> > Generally speaking, we've been conservative about it, and only added
>> > accounts we were sure of.
>>
>> Ah, I didn't make myself clear. I'm more interested in the process going
>> forward, for new access requests. Anyone can create an account and
>> request access; how does a maintainer verify the request? For our
>> purposes it's basically just matching againt the email addresses in
>> existing commits in the repo.
>
> It's a fair question. If you want to verify that someone is
> @intel.com, maybe get them to email you out-of-band to check it. If
> you want to check something else, just ask an admin I suppose.
I thought you wanted not to be bothered with access requests! ;D
BR,
Jani.
--
Jani Nikula, Intel
^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: drm-misc migration to Gitlab server
2024-02-26 12:03 ` Jani Nikula
@ 2024-02-26 12:09 ` Daniel Stone
0 siblings, 0 replies; 32+ messages in thread
From: Daniel Stone @ 2024-02-26 12:09 UTC (permalink / raw)
To: Jani Nikula
Cc: Maxime Ripard, dri-devel, Daniel Vetter, David Airlie,
Maarten Lankhorst, Thomas Zimmermann, Daniel Stone
On Mon, 26 Feb 2024 at 12:03, Jani Nikula <jani.nikula@linux.intel.com> wrote:
> On Mon, 26 Feb 2024, Daniel Stone <daniel@fooishbar.org> wrote:
> > It's a fair question. If you want to verify that someone is
> > @intel.com, maybe get them to email you out-of-band to check it. If
> > you want to check something else, just ask an admin I suppose.
>
> I thought you wanted not to be bothered with access requests! ;D
Hey, we have like four other people with GitLab admin privileges ... I
just want to not have to deal with LDAP mainly.
^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: drm-misc migration to Gitlab server
2024-02-26 12:00 ` Daniel Stone
2024-02-26 12:03 ` Jani Nikula
@ 2024-02-26 13:14 ` Maxime Ripard
1 sibling, 0 replies; 32+ messages in thread
From: Maxime Ripard @ 2024-02-26 13:14 UTC (permalink / raw)
To: Daniel Stone
Cc: Jani Nikula, dri-devel, Daniel Vetter, David Airlie,
Maarten Lankhorst, Thomas Zimmermann, Daniel Stone
[-- Attachment #1: Type: text/plain, Size: 1719 bytes --]
On Mon, Feb 26, 2024 at 12:00:15PM +0000, Daniel Stone wrote:
> On Mon, 26 Feb 2024 at 11:57, Jani Nikula <jani.nikula@linux.intel.com> wrote:
> > On Mon, 26 Feb 2024, Maxime Ripard <mripard@kernel.org> wrote:
> > > For the recent-ish subscriptions, it's possible since we've required to
> > > open a Gitlab issue for a while, so we have the association between the
> > > Gitlab account and the SSH account already.
> > >
> > > During the Gitlab setup, the groups were also created already with the
> > > people that had an SSH account at the time, and Gitlab account.
> > >
> > > But for the rest, yeah, I had to ping Daniel S. about it. He could find
> > > a few matches, but there's some where we just don't know if or what the
> > > Gitlab account is.
> > >
> > > Generally speaking, we've been conservative about it, and only added
> > > accounts we were sure of.
> >
> > Ah, I didn't make myself clear. I'm more interested in the process going
> > forward, for new access requests. Anyone can create an account and
> > request access; how does a maintainer verify the request? For our
> > purposes it's basically just matching againt the email addresses in
> > existing commits in the repo.
>
> It's a fair question. If you want to verify that someone is
> @intel.com, maybe get them to email you out-of-band to check it. If
> you want to check something else, just ask an admin I suppose.
It looks like we can make the email verification mandatory:
https://docs.gitlab.com/ee/security/email_verification.html
And we can have a public email on the profile. I guess requesting the
public email of a profile to match their contribution and be verified
would be enough?
Maxime
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
^ permalink raw reply [flat|nested] 32+ messages in thread
* [dim PATCH] dim: drm-misc: Membership requests now go through Gitlab
2024-02-20 8:49 drm-misc migration to Gitlab server Maxime Ripard
2024-02-20 9:04 ` Maxime Ripard
2024-02-26 11:33 ` Jani Nikula
@ 2024-02-26 11:36 ` Maxime Ripard
2024-02-26 11:36 ` [rerere PATCH] nightly.conf: Update the drm-misc repo Maxime Ripard
2024-02-28 14:18 ` drm-misc migration to Gitlab server Daniel Vetter
` (4 subsequent siblings)
7 siblings, 1 reply; 32+ messages in thread
From: Maxime Ripard @ 2024-02-26 11:36 UTC (permalink / raw)
To: dri-devel
Cc: Daniel Vetter, David Airlie, Maarten Lankhorst, Thomas Zimmermann,
Maxime Ripard, Daniel Stone
Now that drm-misc has switched to Gitlab, we don't need to make
newcomers create a legacy SSH account. Gitlab supports access requests,
so let's just use them.
Signed-off-by: Maxime Ripard <mripard@kernel.org>
---
commit-access.rst | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/commit-access.rst b/commit-access.rst
index 539a7906e52a..3b6c1a19aae2 100644
--- a/commit-access.rst
+++ b/commit-access.rst
@@ -31,9 +31,10 @@ below criteria:
- Agrees to use their commit rights in accordance with the documented merge
criteria, tools, processes, and :ref:`code-of-conduct`.
-Apply for an account (and any other account change requests) through
+You can apply for developpers right by requesting access to the `drm/misc`
+subgroup on GitLab
-https://www.freedesktop.org/wiki/AccountRequests/
+https://gitlab.freedesktop.org/drm/misc
and please ping the maintainers if your request is stuck.
--
2.43.2
^ permalink raw reply related [flat|nested] 32+ messages in thread* [rerere PATCH] nightly.conf: Update the drm-misc repo
2024-02-26 11:36 ` [dim PATCH] dim: drm-misc: Membership requests now go through Gitlab Maxime Ripard
@ 2024-02-26 11:36 ` Maxime Ripard
0 siblings, 0 replies; 32+ messages in thread
From: Maxime Ripard @ 2024-02-26 11:36 UTC (permalink / raw)
To: dri-devel
Cc: Daniel Vetter, David Airlie, Maarten Lankhorst, Thomas Zimmermann,
Maxime Ripard, Daniel Stone
drm-misc has moved to gitlab now, so let's update the repo location.
Signed-off-by: Maxime Ripard <mripard@kernel.org>
---
nightly.conf | 8 ++------
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/nightly.conf b/nightly.conf
index c189f2ccad17..0362efd65cf8 100644
--- a/nightly.conf
+++ b/nightly.conf
@@ -37,12 +37,8 @@ https://anongit.freedesktop.org/git/drm/drm-intel
https://anongit.freedesktop.org/git/drm/drm-intel.git
"
drm_tip_repos[drm-misc]="
-ssh://git.freedesktop.org/git/drm/drm-misc
-ssh://git.freedesktop.org/git/drm-misc
-git://anongit.freedesktop.org/drm/drm-misc
-git://anongit.freedesktop.org/drm-misc
-https://anongit.freedesktop.org/git/drm/drm-misc
-https://anongit.freedesktop.org/git/drm/drm-misc.git
+https://gitlab.freedesktop.org/drm/misc/kernel.git
+ssh://git@gitlab.freedesktop.org/drm/misc/kernel.git
"
drm_tip_repos[drm]="
ssh://git.freedesktop.org/git/drm/drm
--
2.43.2
^ permalink raw reply related [flat|nested] 32+ messages in thread
* Re: drm-misc migration to Gitlab server
2024-02-20 8:49 drm-misc migration to Gitlab server Maxime Ripard
` (2 preceding siblings ...)
2024-02-26 11:36 ` [dim PATCH] dim: drm-misc: Membership requests now go through Gitlab Maxime Ripard
@ 2024-02-28 14:18 ` Daniel Vetter
2024-03-01 16:11 ` Maxime Ripard
` (3 subsequent siblings)
7 siblings, 0 replies; 32+ messages in thread
From: Daniel Vetter @ 2024-02-28 14:18 UTC (permalink / raw)
To: Maxime Ripard
Cc: dri-devel, Daniel Vetter, David Airlie, Maarten Lankhorst,
Thomas Zimmermann, Daniel Stone
Hi Maxime
Just wanted to chime in with a big thank your for volunteering to push
this forward! Best vacations when you come back and are surprised that the
5 year old project is magically moving :-)
-Sima
On Tue, Feb 20, 2024 at 09:49:25AM +0100, Maxime Ripard wrote:
> Hi,
>
> As you might have noticed in your mails, Daniel Stone and I have been
> working on adding all the drm-misc maintainers and committers to Gitlab.
>
> The current repository was still in the cgit instance and was creating
> an unnecessary burden on the admins.
>
> For example, any new user had to create an issue and go through Daniel
> to create an cgit account, even though that user already needed to have
> a gitlab account to create the issue in the first place. Adding an SSH
> key was a similar story. By moving to Gitlab, we'll remove most of that
> burden.
>
> This will be mostly transparent to current committers and users: we'll
> still use dim, in the exact same way, the only change will be the URL of
> the repo. This will also be transparent to linux-next, since the
> linux-next branch lives in its own repo and is pushed by dim when
> pushing a branch.
>
> In the next few days, you might notice conflicting notifications. As we
> figured out the drm-misc group and repo structure, we've added members
> at multiple levels and we will clean things up in the next few days. The
> final organization is that every drm-misc committers and maintainer will
> have permissions over the drm-misc group and its projects, so if it's
> not the case please let us know.
>
> # What we do next
>
> ## Adding the a remaining users
>
> I was able to identify most of the users with an account on the old git
> server. However, there's a few I couldn't match with certainty to a
> gitlab account:
>
> * andr2000
> * jsarha
>
> Please let me know your Gitlab user so I can add them to the group.
>
> ## Changing the default location repo
>
> Dim gets its repos list in the drm-rerere nightly.conf file. We will
> need to change that file to match the gitlab repo, and drop the old cgit
> URLs to avoid people pushing to the wrong place once the transition is
> made.
>
> I guess the next merge window is a good time to do so, it's usually a
> quiet time for us and a small disruption would be easier to handle. I'll
> be off-duty during that time too, so I'll have time to handle any
> complication.
>
> ## Updating the documentation
>
> The documentation currently mentions the old process to request a
> drm-misc access. It will all go through Gitlab now, so it will change a
> few things. We will also need to update and move the issue template to
> the new repo to maintain consistency.
>
> I would expect the transition (if everything goes smoothly) to occur in
> the merge-window time frame (11/03 -> 24/03).
>
> Let me know if you have any questions, or if there's anything we missed,
> Maxime
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
^ permalink raw reply [flat|nested] 32+ messages in thread* Re: drm-misc migration to Gitlab server
2024-02-20 8:49 drm-misc migration to Gitlab server Maxime Ripard
` (3 preceding siblings ...)
2024-02-28 14:18 ` drm-misc migration to Gitlab server Daniel Vetter
@ 2024-03-01 16:11 ` Maxime Ripard
2024-03-06 15:29 ` [rerere PATCH v2] nightly.conf: Update the drm-misc repo Maxime Ripard
` (2 subsequent siblings)
7 siblings, 0 replies; 32+ messages in thread
From: Maxime Ripard @ 2024-03-01 16:11 UTC (permalink / raw)
To: dri-devel
Cc: Daniel Vetter, David Airlie, Maarten Lankhorst, Thomas Zimmermann,
Daniel Stone
[-- Attachment #1: Type: text/plain, Size: 1788 bytes --]
Hi,
On Tue, Feb 20, 2024 at 09:49:25AM +0100, Maxime Ripard wrote:
> ## Changing the default location repo
>
> Dim gets its repos list in the drm-rerere nightly.conf file. We will
> need to change that file to match the gitlab repo, and drop the old cgit
> URLs to avoid people pushing to the wrong place once the transition is
> made.
>
> I guess the next merge window is a good time to do so, it's usually a
> quiet time for us and a small disruption would be easier to handle. I'll
> be off-duty during that time too, so I'll have time to handle any
> complication.
Looking back at the drm.git transition this week, there's probably some
adjustments to make.
First, we shouldn't remove the old repos URLs from nightly.conf entirely
but use the drm_old_urls array we now have to migrate people seamlessly
over time.
Since a lot of people are going to commit compared to drm though, it's
probably best to setup the cgit drm-misc repo as a mirror / read-only
right away and just before committing the nightly.conf modifications.
This way we will avoid a duplication of drm-misc if someone for some
reason didn't switch to the new URL.
And then there's the drm-tip topic. drm-tip at the moment gives write
access to the drm, drm-intel, drm-misc and drm-xe committers. All these
have the gitlab groups setup but drm-intel.
The best scenario would have been to migrate drm-tip before drm-misc so
we don't have a period of time where some people that could have been
granted privileges on the gitlab side wouldn't have cgit credentials,
and thus wouldn't be able to push to drm-tip.
However, it's not clear yet how drm-intel wants to set things up, so we
might have to do that still. Or do both at the same time, for additional
fun.
Maxime
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
^ permalink raw reply [flat|nested] 32+ messages in thread* [rerere PATCH v2] nightly.conf: Update the drm-misc repo
2024-02-20 8:49 drm-misc migration to Gitlab server Maxime Ripard
` (4 preceding siblings ...)
2024-03-01 16:11 ` Maxime Ripard
@ 2024-03-06 15:29 ` Maxime Ripard
2024-03-06 15:38 ` [PATCH v2 1/2] MAINTAINERS: Update drm-misc.git URL Maxime Ripard
2024-03-12 13:56 ` drm-misc migration to Gitlab server Maxime Ripard
7 siblings, 0 replies; 32+ messages in thread
From: Maxime Ripard @ 2024-03-06 15:29 UTC (permalink / raw)
To: dri-devel
Cc: Daniel Vetter, David Airlie, Maarten Lankhorst, Thomas Zimmermann,
Maxime Ripard, Daniel Stone
drm-misc has moved to gitlab now, so let's update the repo location.
Signed-off-by: Maxime Ripard <mripard@kernel.org>
---
nightly.conf | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/nightly.conf b/nightly.conf
index b851af21929a..ab58579c8006 100644
--- a/nightly.conf
+++ b/nightly.conf
@@ -40,10 +40,15 @@ git://anongit.freedesktop.org/drm/drm-intel
git://anongit.freedesktop.org/drm-intel
https://anongit.freedesktop.org/git/drm/drm-intel
https://anongit.freedesktop.org/git/drm/drm-intel.git
"
drm_tip_repos[drm-misc]="
+git@gitlab.freedesktop.org:drm/misc/kernel.git
+https://gitlab.freedesktop.org/drm/misc/kernel.git
+ssh://git@gitlab.freedesktop.org/drm/misc/kernel.git
+"
+drm_old_urls[drm-misc]="
ssh://git.freedesktop.org/git/drm/drm-misc
ssh://git.freedesktop.org/git/drm-misc
git://anongit.freedesktop.org/drm/drm-misc
git://anongit.freedesktop.org/drm-misc
https://anongit.freedesktop.org/git/drm/drm-misc
--
2.43.2
^ permalink raw reply related [flat|nested] 32+ messages in thread* [PATCH v2 1/2] MAINTAINERS: Update drm-misc.git URL
2024-02-20 8:49 drm-misc migration to Gitlab server Maxime Ripard
` (5 preceding siblings ...)
2024-03-06 15:29 ` [rerere PATCH v2] nightly.conf: Update the drm-misc repo Maxime Ripard
@ 2024-03-06 15:38 ` Maxime Ripard
2024-03-06 15:38 ` [PATCH v2 2/2] MAINTAINERS: Update drm-misc web page Maxime Ripard
2024-03-12 13:56 ` drm-misc migration to Gitlab server Maxime Ripard
7 siblings, 1 reply; 32+ messages in thread
From: Maxime Ripard @ 2024-03-06 15:38 UTC (permalink / raw)
To: dri-devel
Cc: Daniel Vetter, David Airlie, Maarten Lankhorst, Thomas Zimmermann,
Maxime Ripard, Daniel Stone
Now that the drm-misc tree has moved to Gitlab, adjust the MAINTAINERS
git trees to reflect the location change.
Signed-off-by: Maxime Ripard <mripard@kernel.org>
---
MAINTAINERS | 172 ++++++++++++++++++++++++++--------------------------
1 file changed, 86 insertions(+), 86 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 2a95919fbc3d..d4e33b3a3bc0 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -1649,11 +1649,11 @@ F: drivers/power/reset/arm-versatile-reboot.c
F: drivers/soc/versatile/
ARM KOMEDA DRM-KMS DRIVER
M: Liviu Dudau <liviu.dudau@arm.com>
S: Supported
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: Documentation/devicetree/bindings/display/arm,komeda.yaml
F: Documentation/gpu/komeda-kms.rst
F: drivers/gpu/drm/arm/display/include/
F: drivers/gpu/drm/arm/display/komeda/
@@ -1661,30 +1661,30 @@ ARM MALI PANFROST DRM DRIVER
M: Boris Brezillon <boris.brezillon@collabora.com>
M: Rob Herring <robh@kernel.org>
R: Steven Price <steven.price@arm.com>
L: dri-devel@lists.freedesktop.org
S: Supported
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: Documentation/gpu/panfrost.rst
F: drivers/gpu/drm/panfrost/
F: include/uapi/drm/panfrost_drm.h
ARM MALI PANTHOR DRM DRIVER
M: Boris Brezillon <boris.brezillon@collabora.com>
M: Steven Price <steven.price@arm.com>
M: Liviu Dudau <liviu.dudau@arm.com>
L: dri-devel@lists.freedesktop.org
S: Supported
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: Documentation/devicetree/bindings/gpu/arm,mali-valhall-csf.yaml
F: drivers/gpu/drm/panthor/
F: include/uapi/drm/panthor_drm.h
ARM MALI-DP DRM DRIVER
M: Liviu Dudau <liviu.dudau@arm.com>
S: Supported
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: Documentation/devicetree/bindings/display/arm,malidp.yaml
F: Documentation/gpu/afbc.rst
F: drivers/gpu/drm/arm/
ARM MFM AND FLOPPY DRIVERS
@@ -6268,11 +6268,11 @@ M: Sumit Semwal <sumit.semwal@linaro.org>
M: Christian König <christian.koenig@amd.com>
L: linux-media@vger.kernel.org
L: dri-devel@lists.freedesktop.org
L: linaro-mm-sig@lists.linaro.org (moderated for non-subscribers)
S: Maintained
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: Documentation/driver-api/dma-buf.rst
F: Documentation/userspace-api/dma-buf-alloc-exchange.rst
F: drivers/dma-buf/
F: include/linux/*fence.h
F: include/linux/dma-buf.h
@@ -6322,11 +6322,11 @@ R: John Stultz <jstultz@google.com>
R: T.J. Mercier <tjmercier@google.com>
L: linux-media@vger.kernel.org
L: dri-devel@lists.freedesktop.org
L: linaro-mm-sig@lists.linaro.org (moderated for non-subscribers)
S: Maintained
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: drivers/dma-buf/dma-heap.c
F: drivers/dma-buf/heaps/*
F: include/linux/dma-heap.h
F: include/uapi/linux/dma-heap.h
@@ -6530,11 +6530,11 @@ F: include/linux/power/smartreflex.h
DRM ACCEL DRIVERS FOR INTEL VPU
M: Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>
M: Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>
L: dri-devel@lists.freedesktop.org
S: Supported
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: drivers/accel/ivpu/
F: include/uapi/drm/ivpu_accel.h
DRM COMPUTE ACCELERATORS DRIVERS AND FRAMEWORK
M: Oded Gabbay <ogabbay@kernel.org>
@@ -6550,47 +6550,47 @@ DRM DRIVER FOR ALLWINNER DE2 AND DE3 ENGINE
M: Maxime Ripard <mripard@kernel.org>
M: Chen-Yu Tsai <wens@csie.org>
R: Jernej Skrabec <jernej.skrabec@gmail.com>
L: dri-devel@lists.freedesktop.org
S: Supported
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: drivers/gpu/drm/sun4i/sun8i*
DRM DRIVER FOR ARM PL111 CLCD
S: Orphan
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: drivers/gpu/drm/pl111/
DRM DRIVER FOR ARM VERSATILE TFT PANELS
M: Linus Walleij <linus.walleij@linaro.org>
S: Maintained
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: Documentation/devicetree/bindings/display/panel/arm,versatile-tft-panel.yaml
F: drivers/gpu/drm/panel/panel-arm-versatile.c
DRM DRIVER FOR ASPEED BMC GFX
M: Joel Stanley <joel@jms.id.au>
L: linux-aspeed@lists.ozlabs.org (moderated for non-subscribers)
S: Supported
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: Documentation/devicetree/bindings/gpu/aspeed-gfx.txt
F: drivers/gpu/drm/aspeed/
DRM DRIVER FOR AST SERVER GRAPHICS CHIPS
M: Dave Airlie <airlied@redhat.com>
R: Thomas Zimmermann <tzimmermann@suse.de>
R: Jocelyn Falempe <jfalempe@redhat.com>
L: dri-devel@lists.freedesktop.org
S: Supported
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: drivers/gpu/drm/ast/
DRM DRIVER FOR BOCHS VIRTUAL GPU
M: Gerd Hoffmann <kraxel@redhat.com>
L: virtualization@lists.linux.dev
S: Maintained
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: drivers/gpu/drm/tiny/bochs.c
DRM DRIVER FOR BOE HIMAX8279D PANELS
M: Jerry Han <hanxu5@huaqin.corp-partner.google.com>
S: Maintained
@@ -6604,18 +6604,18 @@ F: Documentation/devicetree/bindings/display/bridge/chipone,icn6211.yaml
F: drivers/gpu/drm/bridge/chipone-icn6211.c
DRM DRIVER FOR EBBG FT8719 PANEL
M: Joel Selvaraj <jo@jsfamily.in>
S: Maintained
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: Documentation/devicetree/bindings/display/panel/ebbg,ft8719.yaml
F: drivers/gpu/drm/panel/panel-ebbg-ft8719.c
DRM DRIVER FOR FARADAY TVE200 TV ENCODER
M: Linus Walleij <linus.walleij@linaro.org>
S: Maintained
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: drivers/gpu/drm/tve200/
DRM DRIVER FOR FEIXIN K101 IM2BA02 MIPI-DSI LCD PANELS
M: Icenowy Zheng <icenowy@aosc.io>
S: Maintained
@@ -6631,11 +6631,11 @@ F: drivers/gpu/drm/panel/panel-feiyang-fy07024di26a30d.c
DRM DRIVER FOR FIRMWARE FRAMEBUFFERS
M: Thomas Zimmermann <tzimmermann@suse.de>
M: Javier Martinez Canillas <javierm@redhat.com>
L: dri-devel@lists.freedesktop.org
S: Maintained
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: drivers/gpu/drm/drm_aperture.c
F: drivers/gpu/drm/tiny/ofdrm.c
F: drivers/gpu/drm/tiny/simpledrm.c
F: drivers/video/aperture.c
F: drivers/video/nomodeset.c
@@ -6650,53 +6650,53 @@ F: drivers/gpu/drm/panel/panel-edp.c
DRM DRIVER FOR GENERIC USB DISPLAY
M: Noralf Trønnes <noralf@tronnes.org>
S: Maintained
W: https://github.com/notro/gud/wiki
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: drivers/gpu/drm/gud/
F: include/drm/gud.h
DRM DRIVER FOR GRAIN MEDIA GM12U320 PROJECTORS
M: Hans de Goede <hdegoede@redhat.com>
S: Maintained
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: drivers/gpu/drm/tiny/gm12u320.c
DRM DRIVER FOR HIMAX HX8394 MIPI-DSI LCD panels
M: Ondrej Jirman <megi@xff.cz>
M: Javier Martinez Canillas <javierm@redhat.com>
S: Maintained
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: Documentation/devicetree/bindings/display/panel/himax,hx8394.yaml
F: drivers/gpu/drm/panel/panel-himax-hx8394.c
DRM DRIVER FOR HX8357D PANELS
S: Orphan
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: Documentation/devicetree/bindings/display/himax,hx8357d.txt
F: drivers/gpu/drm/tiny/hx8357d.c
DRM DRIVER FOR HYPERV SYNTHETIC VIDEO DEVICE
M: Deepak Rawat <drawat.floss@gmail.com>
L: linux-hyperv@vger.kernel.org
L: dri-devel@lists.freedesktop.org
S: Maintained
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: drivers/gpu/drm/hyperv
DRM DRIVER FOR ILITEK ILI9225 PANELS
M: David Lechner <david@lechnology.com>
S: Maintained
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: Documentation/devicetree/bindings/display/ilitek,ili9225.txt
F: drivers/gpu/drm/tiny/ili9225.c
DRM DRIVER FOR ILITEK ILI9486 PANELS
M: Kamlesh Gurudasani <kamlesh.gurudasani@gmail.com>
S: Maintained
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: Documentation/devicetree/bindings/display/ilitek,ili9486.yaml
F: drivers/gpu/drm/tiny/ili9486.c
DRM DRIVER FOR ILITEK ILI9805 PANELS
M: Michael Trimarchi <michael@amarulasolutions.com>
@@ -6711,18 +6711,18 @@ F: Documentation/devicetree/bindings/display/panel/jadard,jd9365da-h3.yaml
F: drivers/gpu/drm/panel/panel-jadard-jd9365da-h3.c
DRM DRIVER FOR LOGICVC DISPLAY CONTROLLER
M: Paul Kocialkowski <paul.kocialkowski@bootlin.com>
S: Supported
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: drivers/gpu/drm/logicvc/
DRM DRIVER FOR LVDS PANELS
M: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
L: dri-devel@lists.freedesktop.org
S: Maintained
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: Documentation/devicetree/bindings/display/lvds.yaml
F: Documentation/devicetree/bindings/display/panel/panel-lvds.yaml
F: drivers/gpu/drm/panel/panel-lvds.c
DRM DRIVER FOR MANTIX MLAF057WE51 PANELS
@@ -6736,25 +6736,25 @@ DRM DRIVER FOR MGA G200 GRAPHICS CHIPS
M: Dave Airlie <airlied@redhat.com>
R: Thomas Zimmermann <tzimmermann@suse.de>
R: Jocelyn Falempe <jfalempe@redhat.com>
L: dri-devel@lists.freedesktop.org
S: Supported
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: drivers/gpu/drm/mgag200/
DRM DRIVER FOR MI0283QT
M: Noralf Trønnes <noralf@tronnes.org>
S: Maintained
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: Documentation/devicetree/bindings/display/multi-inno,mi0283qt.txt
F: drivers/gpu/drm/tiny/mi0283qt.c
DRM DRIVER FOR MIPI DBI compatible panels
M: Noralf Trønnes <noralf@tronnes.org>
S: Maintained
W: https://github.com/notro/panel-mipi-dbi/wiki
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: Documentation/devicetree/bindings/display/panel/panel-mipi-dbi-spi.yaml
F: drivers/gpu/drm/tiny/panel-mipi-dbi.c
DRM DRIVER FOR MSM ADRENO GPU
M: Rob Clark <robdclark@gmail.com>
@@ -6774,32 +6774,32 @@ F: drivers/gpu/drm/msm/
F: include/uapi/drm/msm_drm.h
DRM DRIVER FOR NOVATEK NT35510 PANELS
M: Linus Walleij <linus.walleij@linaro.org>
S: Maintained
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: Documentation/devicetree/bindings/display/panel/novatek,nt35510.yaml
F: drivers/gpu/drm/panel/panel-novatek-nt35510.c
DRM DRIVER FOR NOVATEK NT35560 PANELS
M: Linus Walleij <linus.walleij@linaro.org>
S: Maintained
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: Documentation/devicetree/bindings/display/panel/sony,acx424akp.yaml
F: drivers/gpu/drm/panel/panel-novatek-nt35560.c
DRM DRIVER FOR NOVATEK NT36523 PANELS
M: Jianhua Lu <lujianhua000@gmail.com>
S: Maintained
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: Documentation/devicetree/bindings/display/panel/novatek,nt36523.yaml
F: drivers/gpu/drm/panel/panel-novatek-nt36523.c
DRM DRIVER FOR NOVATEK NT36672A PANELS
M: Sumit Semwal <sumit.semwal@linaro.org>
S: Maintained
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: Documentation/devicetree/bindings/display/panel/novatek,nt36672a.yaml
F: drivers/gpu/drm/panel/panel-novatek-nt36672a.c
DRM DRIVER FOR NVIDIA GEFORCE/QUADRO GPUS
M: Karol Herbst <kherbst@redhat.com>
@@ -6829,30 +6829,30 @@ F: Documentation/devicetree/bindings/display/bridge/ps8640.yaml
F: drivers/gpu/drm/bridge/parade-ps8640.c
DRM DRIVER FOR PERVASIVE DISPLAYS REPAPER PANELS
M: Noralf Trønnes <noralf@tronnes.org>
S: Maintained
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: Documentation/devicetree/bindings/display/repaper.txt
F: drivers/gpu/drm/tiny/repaper.c
DRM DRIVER FOR QEMU'S CIRRUS DEVICE
M: Dave Airlie <airlied@redhat.com>
M: Gerd Hoffmann <kraxel@redhat.com>
L: virtualization@lists.linux.dev
S: Obsolete
W: https://www.kraxel.org/blog/2014/10/qemu-using-cirrus-considered-harmful/
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: drivers/gpu/drm/tiny/cirrus.c
DRM DRIVER FOR QXL VIRTUAL GPU
M: Dave Airlie <airlied@redhat.com>
M: Gerd Hoffmann <kraxel@redhat.com>
L: virtualization@lists.linux.dev
L: spice-devel@lists.freedesktop.org
S: Maintained
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: drivers/gpu/drm/qxl/
F: include/uapi/drm/qxl_drm.h
DRM DRIVER FOR RAYDIUM RM67191 PANELS
M: Robert Chiras <robert.chiras@nxp.com>
@@ -6861,20 +6861,20 @@ F: Documentation/devicetree/bindings/display/panel/raydium,rm67191.yaml
F: drivers/gpu/drm/panel/panel-raydium-rm67191.c
DRM DRIVER FOR SAMSUNG DB7430 PANELS
M: Linus Walleij <linus.walleij@linaro.org>
S: Maintained
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: Documentation/devicetree/bindings/display/panel/samsung,lms397kf04.yaml
F: drivers/gpu/drm/panel/panel-samsung-db7430.c
DRM DRIVER FOR SAMSUNG MIPI DSIM BRIDGE
M: Inki Dae <inki.dae@samsung.com>
M: Jagan Teki <jagan@amarulasolutions.com>
M: Marek Szyprowski <m.szyprowski@samsung.com>
S: Maintained
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: Documentation/devicetree/bindings/display/bridge/samsung,mipi-dsim.yaml
F: drivers/gpu/drm/bridge/samsung-dsim.c
F: include/drm/bridge/samsung-dsim.h
DRM DRIVER FOR SAMSUNG S6D27A1 PANELS
@@ -6890,11 +6890,11 @@ F: Documentation/devicetree/bindings/display/panel/samsung,s6d7aa0.yaml
F: drivers/gpu/drm/panel/panel-samsung-s6d7aa0.c
DRM DRIVER FOR SITRONIX ST7586 PANELS
M: David Lechner <david@lechnology.com>
S: Maintained
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: Documentation/devicetree/bindings/display/sitronix,st7586.txt
F: drivers/gpu/drm/tiny/st7586.c
DRM DRIVER FOR SITRONIX ST7701 PANELS
M: Jagan Teki <jagan@amarulasolutions.com>
@@ -6911,26 +6911,26 @@ F: Documentation/devicetree/bindings/display/panel/rocktech,jh057n00900.yaml
F: drivers/gpu/drm/panel/panel-sitronix-st7703.c
DRM DRIVER FOR SITRONIX ST7735R PANELS
M: David Lechner <david@lechnology.com>
S: Maintained
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: Documentation/devicetree/bindings/display/sitronix,st7735r.yaml
F: drivers/gpu/drm/tiny/st7735r.c
DRM DRIVER FOR SOLOMON SSD130X OLED DISPLAYS
M: Javier Martinez Canillas <javierm@redhat.com>
S: Maintained
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: Documentation/devicetree/bindings/display/solomon,ssd-common.yaml
F: Documentation/devicetree/bindings/display/solomon,ssd13*.yaml
F: drivers/gpu/drm/solomon/ssd130x*
DRM DRIVER FOR ST-ERICSSON MCDE
M: Linus Walleij <linus.walleij@linaro.org>
S: Maintained
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: Documentation/devicetree/bindings/display/ste,mcde.yaml
F: drivers/gpu/drm/mcde/
DRM DRIVER FOR SYNAPTICS R63353 PANELS
M: Michael Trimarchi <michael@amarulasolutions.com>
@@ -6950,55 +6950,55 @@ F: Documentation/devicetree/bindings/display/bridge/ti,sn65dsi86.yaml
F: drivers/gpu/drm/bridge/ti-sn65dsi86.c
DRM DRIVER FOR TPO TPG110 PANELS
M: Linus Walleij <linus.walleij@linaro.org>
S: Maintained
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: Documentation/devicetree/bindings/display/panel/tpo,tpg110.yaml
F: drivers/gpu/drm/panel/panel-tpo-tpg110.c
DRM DRIVER FOR USB DISPLAYLINK VIDEO ADAPTERS
M: Dave Airlie <airlied@redhat.com>
R: Sean Paul <sean@poorly.run>
R: Thomas Zimmermann <tzimmermann@suse.de>
L: dri-devel@lists.freedesktop.org
S: Supported
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: drivers/gpu/drm/udl/
DRM DRIVER FOR VIRTUAL KERNEL MODESETTING (VKMS)
M: Rodrigo Siqueira <rodrigosiqueiramelo@gmail.com>
M: Melissa Wen <melissa.srw@gmail.com>
M: Maíra Canal <mairacanal@riseup.net>
R: Haneen Mohammed <hamohammed.sa@gmail.com>
R: Daniel Vetter <daniel@ffwll.ch>
L: dri-devel@lists.freedesktop.org
S: Maintained
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: Documentation/gpu/vkms.rst
F: drivers/gpu/drm/vkms/
DRM DRIVER FOR VIRTUALBOX VIRTUAL GPU
M: Hans de Goede <hdegoede@redhat.com>
L: dri-devel@lists.freedesktop.org
S: Maintained
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: drivers/gpu/drm/vboxvideo/
DRM DRIVER FOR VMWARE VIRTUAL GPU
M: Zack Rusin <zack.rusin@broadcom.com>
R: Broadcom internal kernel review list <bcm-kernel-feedback-list@broadcom.com>
L: dri-devel@lists.freedesktop.org
S: Supported
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: drivers/gpu/drm/vmwgfx/
F: include/uapi/drm/vmwgfx_drm.h
DRM DRIVER FOR WIDECHIPS WS2401 PANELS
M: Linus Walleij <linus.walleij@linaro.org>
S: Maintained
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: Documentation/devicetree/bindings/display/panel/samsung,lms380kf01.yaml
F: drivers/gpu/drm/panel/panel-widechips-ws2401.c
DRM DRIVERS
M: David Airlie <airlied@gmail.com>
@@ -7020,11 +7020,11 @@ DRM DRIVERS AND MISC GPU PATCHES
M: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
M: Maxime Ripard <mripard@kernel.org>
M: Thomas Zimmermann <tzimmermann@suse.de>
S: Maintained
W: https://01.org/linuxgraphics/gfx-docs/maintainer-tools/drm-misc.html
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: Documentation/devicetree/bindings/display/
F: Documentation/devicetree/bindings/gpu/
F: Documentation/gpu/
F: drivers/gpu/drm/
F: drivers/gpu/vga/
@@ -7047,21 +7047,21 @@ X: drivers/gpu/drm/tegra/
DRM DRIVERS FOR ALLWINNER A10
M: Maxime Ripard <mripard@kernel.org>
M: Chen-Yu Tsai <wens@csie.org>
L: dri-devel@lists.freedesktop.org
S: Supported
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: Documentation/devicetree/bindings/display/allwinner*
F: drivers/gpu/drm/sun4i/
DRM DRIVERS FOR AMLOGIC SOCS
M: Neil Armstrong <neil.armstrong@linaro.org>
L: dri-devel@lists.freedesktop.org
L: linux-amlogic@lists.infradead.org
S: Supported
W: http://linux-meson.com/
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: Documentation/devicetree/bindings/display/amlogic,meson-dw-hdmi.yaml
F: Documentation/devicetree/bindings/display/amlogic,meson-vpu.yaml
F: Documentation/gpu/meson.rst
F: drivers/gpu/drm/ci/xfails/meson*
F: drivers/gpu/drm/meson/
@@ -7069,11 +7069,11 @@ F: drivers/gpu/drm/meson/
DRM DRIVERS FOR ATMEL HLCDC
M: Sam Ravnborg <sam@ravnborg.org>
M: Boris Brezillon <bbrezillon@kernel.org>
L: dri-devel@lists.freedesktop.org
S: Supported
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: Documentation/devicetree/bindings/display/atmel/
F: drivers/gpu/drm/atmel-hlcdc/
DRM DRIVERS FOR BRIDGE CHIPS
M: Andrzej Hajda <andrzej.hajda@intel.com>
@@ -7081,11 +7081,11 @@ M: Neil Armstrong <neil.armstrong@linaro.org>
M: Robert Foss <rfoss@kernel.org>
R: Laurent Pinchart <Laurent.pinchart@ideasonboard.com>
R: Jonas Karlman <jonas@kwiboo.se>
R: Jernej Skrabec <jernej.skrabec@gmail.com>
S: Maintained
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: Documentation/devicetree/bindings/display/bridge/
F: drivers/gpu/drm/bridge/
F: drivers/gpu/drm/drm_bridge.c
F: drivers/gpu/drm/drm_bridge_connector.c
F: include/drm/drm_bridge.h
@@ -7106,20 +7106,20 @@ F: include/uapi/drm/exynos_drm.h
DRM DRIVERS FOR FREESCALE DCU
M: Stefan Agner <stefan@agner.ch>
M: Alison Wang <alison.wang@nxp.com>
L: dri-devel@lists.freedesktop.org
S: Supported
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: Documentation/devicetree/bindings/display/fsl,dcu.txt
F: Documentation/devicetree/bindings/display/fsl,tcon.txt
F: drivers/gpu/drm/fsl-dcu/
DRM DRIVERS FOR FREESCALE IMX 5/6
M: Philipp Zabel <p.zabel@pengutronix.de>
L: dri-devel@lists.freedesktop.org
S: Maintained
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
T: git git://git.pengutronix.de/git/pza/linux
F: Documentation/devicetree/bindings/display/imx/
F: drivers/gpu/drm/imx/ipuv3/
F: drivers/gpu/ipu-v3/
@@ -7135,11 +7135,11 @@ F: drivers/gpu/drm/bridge/imx/
DRM DRIVERS FOR GMA500 (Poulsbo, Moorestown and derivative chipsets)
M: Patrik Jakobsson <patrik.r.jakobsson@gmail.com>
L: dri-devel@lists.freedesktop.org
S: Maintained
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: drivers/gpu/drm/gma500/
DRM DRIVERS FOR HISILICON
M: Xinliang Liu <xinliang.liu@linaro.org>
M: Tian Tao <tiantao6@hisilicon.com>
@@ -7147,28 +7147,28 @@ R: Xinwei Kong <kong.kongxinwei@hisilicon.com>
R: Sumit Semwal <sumit.semwal@linaro.org>
R: Yongqin Liu <yongqin.liu@linaro.org>
R: John Stultz <jstultz@google.com>
L: dri-devel@lists.freedesktop.org
S: Maintained
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: Documentation/devicetree/bindings/display/hisilicon/
F: drivers/gpu/drm/hisilicon/
DRM DRIVERS FOR LIMA
M: Qiang Yu <yuq825@gmail.com>
L: dri-devel@lists.freedesktop.org
L: lima@lists.freedesktop.org (moderated for non-subscribers)
S: Maintained
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: drivers/gpu/drm/lima/
F: include/uapi/drm/lima_drm.h
DRM DRIVERS FOR LOONGSON
M: Sui Jingfeng <suijingfeng@loongson.cn>
L: dri-devel@lists.freedesktop.org
S: Supported
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: drivers/gpu/drm/loongson/
DRM DRIVERS FOR MEDIATEK
M: Chun-Kuang Hu <chunkuang.hu@kernel.org>
M: Philipp Zabel <p.zabel@pengutronix.de>
@@ -7212,96 +7212,96 @@ F: drivers/gpu/drm/renesas/rcar-du/
DRM DRIVERS FOR RENESAS RZ
M: Biju Das <biju.das.jz@bp.renesas.com>
L: dri-devel@lists.freedesktop.org
L: linux-renesas-soc@vger.kernel.org
S: Maintained
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: Documentation/devicetree/bindings/display/renesas,rzg2l-du.yaml
F: drivers/gpu/drm/renesas/rz-du/
DRM DRIVERS FOR RENESAS SHMOBILE
M: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
M: Geert Uytterhoeven <geert+renesas@glider.be>
L: dri-devel@lists.freedesktop.org
L: linux-renesas-soc@vger.kernel.org
S: Supported
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: Documentation/devicetree/bindings/display/renesas,shmobile-lcdc.yaml
F: drivers/gpu/drm/renesas/shmobile/
F: include/linux/platform_data/shmob_drm.h
DRM DRIVERS FOR ROCKCHIP
M: Sandy Huang <hjc@rock-chips.com>
M: Heiko Stübner <heiko@sntech.de>
M: Andy Yan <andy.yan@rock-chips.com>
L: dri-devel@lists.freedesktop.org
S: Maintained
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: Documentation/devicetree/bindings/display/rockchip/
F: drivers/gpu/drm/ci/xfails/rockchip*
F: drivers/gpu/drm/rockchip/
DRM DRIVERS FOR STI
M: Alain Volmat <alain.volmat@foss.st.com>
L: dri-devel@lists.freedesktop.org
S: Maintained
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: Documentation/devicetree/bindings/display/st,stih4xx.txt
F: drivers/gpu/drm/sti
DRM DRIVERS FOR STM
M: Yannick Fertre <yannick.fertre@foss.st.com>
M: Raphael Gallais-Pou <raphael.gallais-pou@foss.st.com>
M: Philippe Cornu <philippe.cornu@foss.st.com>
L: dri-devel@lists.freedesktop.org
S: Maintained
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: Documentation/devicetree/bindings/display/st,stm32-ltdc.yaml
F: drivers/gpu/drm/stm
DRM DRIVERS FOR TI KEYSTONE
M: Jyri Sarha <jyri.sarha@iki.fi>
M: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
L: dri-devel@lists.freedesktop.org
S: Maintained
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: Documentation/devicetree/bindings/display/ti/ti,am65x-dss.yaml
F: Documentation/devicetree/bindings/display/ti/ti,j721e-dss.yaml
F: Documentation/devicetree/bindings/display/ti/ti,k2g-dss.yaml
F: drivers/gpu/drm/tidss/
DRM DRIVERS FOR TI LCDC
M: Jyri Sarha <jyri.sarha@iki.fi>
M: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
L: dri-devel@lists.freedesktop.org
S: Maintained
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: Documentation/devicetree/bindings/display/tilcdc/
F: drivers/gpu/drm/tilcdc/
DRM DRIVERS FOR TI OMAP
M: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
L: dri-devel@lists.freedesktop.org
S: Maintained
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: Documentation/devicetree/bindings/display/ti/
F: drivers/gpu/drm/omapdrm/
DRM DRIVERS FOR V3D
M: Melissa Wen <mwen@igalia.com>
M: Maíra Canal <mcanal@igalia.com>
S: Supported
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: Documentation/devicetree/bindings/gpu/brcm,bcm-v3d.yaml
F: drivers/gpu/drm/v3d/
F: include/uapi/drm/v3d_drm.h
DRM DRIVERS FOR VC4
M: Maxime Ripard <mripard@kernel.org>
S: Supported
T: git git://github.com/anholt/linux
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: Documentation/devicetree/bindings/display/brcm,bcm2835-*.yaml
F: drivers/gpu/drm/vc4/
F: include/uapi/drm/vc4_drm.h
DRM DRIVERS FOR VIVANTE GPU IP
@@ -7318,65 +7318,65 @@ F: include/uapi/drm/etnaviv_drm.h
DRM DRIVERS FOR XEN
M: Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
L: dri-devel@lists.freedesktop.org
L: xen-devel@lists.xenproject.org (moderated for non-subscribers)
S: Supported
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: Documentation/gpu/xen-front.rst
F: drivers/gpu/drm/xen/
DRM DRIVERS FOR XILINX
M: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
L: dri-devel@lists.freedesktop.org
S: Maintained
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: Documentation/devicetree/bindings/display/xlnx/
F: drivers/gpu/drm/xlnx/
DRM GPU SCHEDULER
M: Luben Tuikov <ltuikov89@gmail.com>
M: Matthew Brost <matthew.brost@intel.com>
L: dri-devel@lists.freedesktop.org
S: Maintained
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: drivers/gpu/drm/scheduler/
F: include/drm/gpu_scheduler.h
DRM PANEL DRIVERS
M: Neil Armstrong <neil.armstrong@linaro.org>
R: Jessica Zhang <quic_jesszhan@quicinc.com>
R: Sam Ravnborg <sam@ravnborg.org>
L: dri-devel@lists.freedesktop.org
S: Maintained
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: Documentation/devicetree/bindings/display/panel/
F: drivers/gpu/drm/drm_panel.c
F: drivers/gpu/drm/panel/
F: include/drm/drm_panel.h
DRM PRIVACY-SCREEN CLASS
M: Hans de Goede <hdegoede@redhat.com>
L: dri-devel@lists.freedesktop.org
S: Maintained
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: drivers/gpu/drm/drm_privacy_screen*
F: include/drm/drm_privacy_screen*
DRM TTM SUBSYSTEM
M: Christian Koenig <christian.koenig@amd.com>
M: Huang Rui <ray.huang@amd.com>
L: dri-devel@lists.freedesktop.org
S: Maintained
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: drivers/gpu/drm/ttm/
F: include/drm/ttm/
DRM AUTOMATED TESTING
M: Helen Koike <helen.koike@collabora.com>
L: dri-devel@lists.freedesktop.org
S: Maintained
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: Documentation/gpu/automated_testing.rst
F: drivers/gpu/drm/ci/
DSBR100 USB FM RADIO DRIVER
M: Alexey Klimov <klimov.linux@gmail.com>
@@ -8422,11 +8422,11 @@ W: https://floatingpoint.billm.au/
F: arch/x86/math-emu/
FRAMEBUFFER CORE
M: Daniel Vetter <daniel@ffwll.ch>
S: Odd Fixes
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: drivers/video/fbdev/core/
FRAMEBUFFER LAYER
M: Helge Deller <deller@gmx.de>
L: linux-fbdev@vger.kernel.org
@@ -10494,11 +10494,11 @@ F: drivers/media/rc/img-ir/
IMGTEC POWERVR DRM DRIVER
M: Frank Binns <frank.binns@imgtec.com>
M: Matt Coster <matt.coster@imgtec.com>
S: Supported
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: Documentation/devicetree/bindings/gpu/img,powervr.yaml
F: Documentation/gpu/imagination/
F: drivers/gpu/drm/imagination/
F: include/uapi/drm/pvr_drm.h
@@ -11281,11 +11281,11 @@ F: tools/testing/selftests/iommu/
IOSYS-MAP HELPERS
M: Thomas Zimmermann <tzimmermann@suse.de>
L: dri-devel@lists.freedesktop.org
S: Maintained
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: include/linux/iosys-map.h
IO_URING
M: Jens Axboe <axboe@kernel.dk>
R: Pavel Begunkov <asml.silence@gmail.com>
@@ -11474,11 +11474,11 @@ F: drivers/media/tuners/it913x*
ITE IT66121 HDMI BRIDGE DRIVER
M: Phong LE <ple@baylibre.com>
M: Neil Armstrong <neil.armstrong@linaro.org>
S: Maintained
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: Documentation/devicetree/bindings/display/bridge/ite,it66121.yaml
F: drivers/gpu/drm/bridge/ite-it66121.c
IVTV VIDEO4LINUX DRIVER
M: Andy Walls <awalls@md.metrocast.net>
@@ -15025,11 +15025,11 @@ F: drivers/media/tuners/mxl5007t.*
MXSFB DRM DRIVER
M: Marek Vasut <marex@denx.de>
M: Stefan Agner <stefan@agner.ch>
L: dri-devel@lists.freedesktop.org
S: Supported
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: Documentation/devicetree/bindings/display/fsl,lcdif.yaml
F: drivers/gpu/drm/mxsfb/
MYLEX DAC960 PCI RAID Controller
M: Hannes Reinecke <hare@kernel.org>
@@ -15765,11 +15765,11 @@ F: include/uapi/linux/dw100.h
NXP i.MX 8MQ DCSS DRIVER
M: Laurentiu Palcu <laurentiu.palcu@oss.nxp.com>
R: Lucas Stach <l.stach@pengutronix.de>
L: dri-devel@lists.freedesktop.org
S: Maintained
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: Documentation/devicetree/bindings/display/imx/nxp,imx8mq-dcss.yaml
F: drivers/gpu/drm/imx/dcss/
NXP i.MX 8QXP ADC DRIVER
M: Cai Huoqing <cai.huoqing@linux.dev>
@@ -18074,11 +18074,11 @@ M: Jeffrey Hugo <quic_jhugo@quicinc.com>
R: Carl Vanderlip <quic_carlv@quicinc.com>
R: Pranjal Ramajor Asha Kanojiya <quic_pkanojiy@quicinc.com>
L: linux-arm-msm@vger.kernel.org
L: dri-devel@lists.freedesktop.org
S: Supported
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: Documentation/accel/qaic/
F: drivers/accel/qaic/
F: include/uapi/drm/qaic_accel.h
QUALCOMM CORE POWER REDUCTION (CPR) AVS DRIVER
@@ -21194,11 +21194,11 @@ SYNC FILE FRAMEWORK
M: Sumit Semwal <sumit.semwal@linaro.org>
R: Gustavo Padovan <gustavo@padovan.org>
L: linux-media@vger.kernel.org
L: dri-devel@lists.freedesktop.org
S: Maintained
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: Documentation/driver-api/sync_file.rst
F: drivers/dma-buf/dma-fence*
F: drivers/dma-buf/sw_sync.c
F: drivers/dma-buf/sync_*
F: include/linux/sync_file.h
@@ -22966,11 +22966,11 @@ F: lib/iov_iter.c
USERSPACE DMA BUFFER DRIVER
M: Gerd Hoffmann <kraxel@redhat.com>
L: dri-devel@lists.freedesktop.org
S: Maintained
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: drivers/dma-buf/udmabuf.c
F: include/uapi/linux/udmabuf.h
USERSPACE I/O (UIO)
M: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
@@ -23142,11 +23142,11 @@ S: Maintained
F: drivers/vfio/platform/
VGA_SWITCHEROO
R: Lukas Wunner <lukas@wunner.de>
S: Maintained
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: Documentation/gpu/vga-switcheroo.rst
F: drivers/gpu/vga/vga_switcheroo.c
F: include/linux/vga_switcheroo.h
VIA RHINE NETWORK DRIVER
@@ -23335,11 +23335,11 @@ M: Gerd Hoffmann <kraxel@redhat.com>
R: Gurchetan Singh <gurchetansingh@chromium.org>
R: Chia-I Wu <olvaffe@gmail.com>
L: dri-devel@lists.freedesktop.org
L: virtualization@lists.linux.dev
S: Maintained
-T: git git://anongit.freedesktop.org/drm/drm-misc
+T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: drivers/gpu/drm/ci/xfails/virtio*
F: drivers/gpu/drm/virtio/
F: include/uapi/linux/virtio_gpu.h
VIRTIO HOST (VHOST)
--
2.43.2
^ permalink raw reply related [flat|nested] 32+ messages in thread* [PATCH v2 2/2] MAINTAINERS: Update drm-misc web page
2024-03-06 15:38 ` [PATCH v2 1/2] MAINTAINERS: Update drm-misc.git URL Maxime Ripard
@ 2024-03-06 15:38 ` Maxime Ripard
2024-03-07 14:02 ` Jani Nikula
0 siblings, 1 reply; 32+ messages in thread
From: Maxime Ripard @ 2024-03-06 15:38 UTC (permalink / raw)
To: dri-devel
Cc: Daniel Vetter, David Airlie, Maarten Lankhorst, Thomas Zimmermann,
Maxime Ripard, Daniel Stone
This URL gets redirected to the Intel landing page now. Let's switch the
webpage to freedesktop.
Signed-off-by: Maxime Ripard <mripard@kernel.org>
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index d4e33b3a3bc0..cdd3ddd6efb5 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -7019,11 +7019,11 @@ F: include/uapi/drm/
DRM DRIVERS AND MISC GPU PATCHES
M: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
M: Maxime Ripard <mripard@kernel.org>
M: Thomas Zimmermann <tzimmermann@suse.de>
S: Maintained
-W: https://01.org/linuxgraphics/gfx-docs/maintainer-tools/drm-misc.html
+W: https://drm.pages.freedesktop.org/maintainer-tools/drm-misc.html
T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
F: Documentation/devicetree/bindings/display/
F: Documentation/devicetree/bindings/gpu/
F: Documentation/gpu/
F: drivers/gpu/drm/
--
2.43.2
^ permalink raw reply related [flat|nested] 32+ messages in thread
* Re: [PATCH v2 2/2] MAINTAINERS: Update drm-misc web page
2024-03-06 15:38 ` [PATCH v2 2/2] MAINTAINERS: Update drm-misc web page Maxime Ripard
@ 2024-03-07 14:02 ` Jani Nikula
2024-03-08 9:49 ` Maxime Ripard
0 siblings, 1 reply; 32+ messages in thread
From: Jani Nikula @ 2024-03-07 14:02 UTC (permalink / raw)
To: Maxime Ripard, dri-devel
Cc: Daniel Vetter, David Airlie, Maarten Lankhorst, Thomas Zimmermann,
Maxime Ripard, Daniel Stone
On Wed, 06 Mar 2024, Maxime Ripard <mripard@kernel.org> wrote:
> This URL gets redirected to the Intel landing page now. Let's switch the
> webpage to freedesktop.
>
> Signed-off-by: Maxime Ripard <mripard@kernel.org>
> ---
> MAINTAINERS | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index d4e33b3a3bc0..cdd3ddd6efb5 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -7019,11 +7019,11 @@ F: include/uapi/drm/
> DRM DRIVERS AND MISC GPU PATCHES
> M: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> M: Maxime Ripard <mripard@kernel.org>
> M: Thomas Zimmermann <tzimmermann@suse.de>
> S: Maintained
> -W: https://01.org/linuxgraphics/gfx-docs/maintainer-tools/drm-misc.html
> +W: https://drm.pages.freedesktop.org/maintainer-tools/drm-misc.html
Maybe also add bug tracker link?
B: https://gitlab.freedesktop.org/drm/misc/kernel/-/issues
> T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
> F: Documentation/devicetree/bindings/display/
> F: Documentation/devicetree/bindings/gpu/
> F: Documentation/gpu/
> F: drivers/gpu/drm/
--
Jani Nikula, Intel
^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: [PATCH v2 2/2] MAINTAINERS: Update drm-misc web page
2024-03-07 14:02 ` Jani Nikula
@ 2024-03-08 9:49 ` Maxime Ripard
0 siblings, 0 replies; 32+ messages in thread
From: Maxime Ripard @ 2024-03-08 9:49 UTC (permalink / raw)
To: Jani Nikula
Cc: dri-devel, Daniel Vetter, David Airlie, Maarten Lankhorst,
Thomas Zimmermann, Daniel Stone
[-- Attachment #1: Type: text/plain, Size: 1198 bytes --]
Hi Jani,
On Thu, Mar 07, 2024 at 04:02:02PM +0200, Jani Nikula wrote:
> On Wed, 06 Mar 2024, Maxime Ripard <mripard@kernel.org> wrote:
> > This URL gets redirected to the Intel landing page now. Let's switch the
> > webpage to freedesktop.
> >
> > Signed-off-by: Maxime Ripard <mripard@kernel.org>
> > ---
> > MAINTAINERS | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index d4e33b3a3bc0..cdd3ddd6efb5 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -7019,11 +7019,11 @@ F: include/uapi/drm/
> > DRM DRIVERS AND MISC GPU PATCHES
> > M: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> > M: Maxime Ripard <mripard@kernel.org>
> > M: Thomas Zimmermann <tzimmermann@suse.de>
> > S: Maintained
> > -W: https://01.org/linuxgraphics/gfx-docs/maintainer-tools/drm-misc.html
> > +W: https://drm.pages.freedesktop.org/maintainer-tools/drm-misc.html
>
> Maybe also add bug tracker link?
>
> B: https://gitlab.freedesktop.org/drm/misc/kernel/-/issues
That's a good idea indeed, but I'm not sure if we would need to set it
up here or under every driver part of the drm-misc tree?
Maxime
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: drm-misc migration to Gitlab server
2024-02-20 8:49 drm-misc migration to Gitlab server Maxime Ripard
` (6 preceding siblings ...)
2024-03-06 15:38 ` [PATCH v2 1/2] MAINTAINERS: Update drm-misc.git URL Maxime Ripard
@ 2024-03-12 13:56 ` Maxime Ripard
2024-04-01 16:49 ` Tvrtko Ursulin
7 siblings, 1 reply; 32+ messages in thread
From: Maxime Ripard @ 2024-03-12 13:56 UTC (permalink / raw)
To: dri-devel
Cc: Daniel Vetter, David Airlie, Maarten Lankhorst, Thomas Zimmermann,
Daniel Stone
[-- Attachment #1: Type: text/plain, Size: 1219 bytes --]
Hi,
On Tue, Feb 20, 2024 at 09:49:25AM +0100, Maxime Ripard wrote:
> ## Changing the default location repo
>
> Dim gets its repos list in the drm-rerere nightly.conf file. We will
> need to change that file to match the gitlab repo, and drop the old cgit
> URLs to avoid people pushing to the wrong place once the transition is
> made.
>
> I guess the next merge window is a good time to do so, it's usually a
> quiet time for us and a small disruption would be easier to handle. I'll
> be off-duty during that time too, so I'll have time to handle any
> complication.
>
> ## Updating the documentation
>
> The documentation currently mentions the old process to request a
> drm-misc access. It will all go through Gitlab now, so it will change a
> few things. We will also need to update and move the issue template to
> the new repo to maintain consistency.
>
> I would expect the transition (if everything goes smoothly) to occur in
> the merge-window time frame (11/03 -> 24/03).
The transition just happened. The main drm-misc repo is now on gitlab,
with the old cgit repo being setup as a mirror.
If there's any issue accessing that gitlab repo, please let me know.
Maxime
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
^ permalink raw reply [flat|nested] 32+ messages in thread* Re: drm-misc migration to Gitlab server
2024-03-12 13:56 ` drm-misc migration to Gitlab server Maxime Ripard
@ 2024-04-01 16:49 ` Tvrtko Ursulin
2024-04-29 17:06 ` Helen Koike
0 siblings, 1 reply; 32+ messages in thread
From: Tvrtko Ursulin @ 2024-04-01 16:49 UTC (permalink / raw)
To: Maxime Ripard, dri-devel
Cc: Daniel Vetter, David Airlie, Maarten Lankhorst, Thomas Zimmermann,
Daniel Stone
On 12/03/2024 13:56, Maxime Ripard wrote:
> Hi,
>
> On Tue, Feb 20, 2024 at 09:49:25AM +0100, Maxime Ripard wrote:
>> ## Changing the default location repo
>>
>> Dim gets its repos list in the drm-rerere nightly.conf file. We will
>> need to change that file to match the gitlab repo, and drop the old cgit
>> URLs to avoid people pushing to the wrong place once the transition is
>> made.
>>
>> I guess the next merge window is a good time to do so, it's usually a
>> quiet time for us and a small disruption would be easier to handle. I'll
>> be off-duty during that time too, so I'll have time to handle any
>> complication.
>>
>> ## Updating the documentation
>>
>> The documentation currently mentions the old process to request a
>> drm-misc access. It will all go through Gitlab now, so it will change a
>> few things. We will also need to update and move the issue template to
>> the new repo to maintain consistency.
>>
>> I would expect the transition (if everything goes smoothly) to occur in
>> the merge-window time frame (11/03 -> 24/03).
>
> The transition just happened. The main drm-misc repo is now on gitlab,
> with the old cgit repo being setup as a mirror.
>
> If there's any issue accessing that gitlab repo, please let me know.
No issues accessing the repo just a slight confusion and how to handle
the workflow. More specifically, if I have a patch which wants to be
merged to drm-misc-next, is the mailing list based worklflow still the
way to go, or I should create a merge request, or I should apply for
commit access via some new method other than adding permissions to my
legacy fdo ssh account?
Regards,
Tvrtko
^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: drm-misc migration to Gitlab server
2024-04-01 16:49 ` Tvrtko Ursulin
@ 2024-04-29 17:06 ` Helen Koike
2024-04-29 17:56 ` Jani Nikula
0 siblings, 1 reply; 32+ messages in thread
From: Helen Koike @ 2024-04-29 17:06 UTC (permalink / raw)
To: Tvrtko Ursulin, Maxime Ripard, dri-devel
Cc: Daniel Vetter, David Airlie, Maarten Lankhorst, Thomas Zimmermann,
Daniel Stone
On 01/04/2024 13:49, Tvrtko Ursulin wrote:
>
> On 12/03/2024 13:56, Maxime Ripard wrote:
>> Hi,
>>
>> On Tue, Feb 20, 2024 at 09:49:25AM +0100, Maxime Ripard wrote:
>>> ## Changing the default location repo
>>>
>>> Dim gets its repos list in the drm-rerere nightly.conf file. We will
>>> need to change that file to match the gitlab repo, and drop the old cgit
>>> URLs to avoid people pushing to the wrong place once the transition is
>>> made.
>>>
>>> I guess the next merge window is a good time to do so, it's usually a
>>> quiet time for us and a small disruption would be easier to handle. I'll
>>> be off-duty during that time too, so I'll have time to handle any
>>> complication.
>>>
>>> ## Updating the documentation
>>>
>>> The documentation currently mentions the old process to request a
>>> drm-misc access. It will all go through Gitlab now, so it will change a
>>> few things. We will also need to update and move the issue template to
>>> the new repo to maintain consistency.
>>>
>>> I would expect the transition (if everything goes smoothly) to occur in
>>> the merge-window time frame (11/03 -> 24/03).
>>
>> The transition just happened. The main drm-misc repo is now on gitlab,
>> with the old cgit repo being setup as a mirror.
>>
>> If there's any issue accessing that gitlab repo, please let me know.
>
> No issues accessing the repo just a slight confusion and how to handle
> the workflow. More specifically, if I have a patch which wants to be
> merged to drm-misc-next, is the mailing list based worklflow still the
> way to go, or I should create a merge request, or I should apply for
> commit access via some new method other than adding permissions to my
> legacy fdo ssh account?
I have this same question, I thought we would keep the workflow with dim
tool, but after I pointed drm-misc remote to gitlab, dim is not happy.
If I don't point drm-misc to gitlab, dim say it is outdated (but I'm
using the last top of the tree of maintainer-tools).
So I was wondering if dim requires changes or if the workflow changed.
Thanks,
Helen
>
> Regards,
>
> Tvrtko
^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: drm-misc migration to Gitlab server
2024-04-29 17:06 ` Helen Koike
@ 2024-04-29 17:56 ` Jani Nikula
2024-04-29 18:29 ` Helen Koike
0 siblings, 1 reply; 32+ messages in thread
From: Jani Nikula @ 2024-04-29 17:56 UTC (permalink / raw)
To: Helen Koike, Tvrtko Ursulin, Maxime Ripard, dri-devel
Cc: Daniel Vetter, David Airlie, Maarten Lankhorst, Thomas Zimmermann,
Daniel Stone
On Mon, 29 Apr 2024, Helen Koike <helen.koike@collabora.com> wrote:
> On 01/04/2024 13:49, Tvrtko Ursulin wrote:
>> No issues accessing the repo just a slight confusion and how to handle
>> the workflow. More specifically, if I have a patch which wants to be
>> merged to drm-misc-next, is the mailing list based worklflow still the
>> way to go, or I should create a merge request, or I should apply for
>> commit access via some new method other than adding permissions to my
>> legacy fdo ssh account?
>
> I have this same question, I thought we would keep the workflow with dim
> tool, but after I pointed drm-misc remote to gitlab, dim is not happy.
>
> If I don't point drm-misc to gitlab, dim say it is outdated (but I'm
> using the last top of the tree of maintainer-tools).
>
> So I was wondering if dim requires changes or if the workflow changed.
The workflow has not changed, only the location of the repo.
I'm afraid there's insufficient info here to say what exactly is going
on though.
BR,
Jani.
--
Jani Nikula, Intel
^ permalink raw reply [flat|nested] 32+ messages in thread
* Re: drm-misc migration to Gitlab server
2024-04-29 17:56 ` Jani Nikula
@ 2024-04-29 18:29 ` Helen Koike
0 siblings, 0 replies; 32+ messages in thread
From: Helen Koike @ 2024-04-29 18:29 UTC (permalink / raw)
To: Jani Nikula, Tvrtko Ursulin, Maxime Ripard, dri-devel
Cc: Daniel Vetter, David Airlie, Maarten Lankhorst, Thomas Zimmermann,
Daniel Stone
On 29/04/2024 14:56, Jani Nikula wrote:
> On Mon, 29 Apr 2024, Helen Koike <helen.koike@collabora.com> wrote:
>> On 01/04/2024 13:49, Tvrtko Ursulin wrote:
>>> No issues accessing the repo just a slight confusion and how to handle
>>> the workflow. More specifically, if I have a patch which wants to be
>>> merged to drm-misc-next, is the mailing list based worklflow still the
>>> way to go, or I should create a merge request, or I should apply for
>>> commit access via some new method other than adding permissions to my
>>> legacy fdo ssh account?
>>
>> I have this same question, I thought we would keep the workflow with dim
>> tool, but after I pointed drm-misc remote to gitlab, dim is not happy.
>>
>> If I don't point drm-misc to gitlab, dim say it is outdated (but I'm
>> using the last top of the tree of maintainer-tools).
>>
>> So I was wondering if dim requires changes or if the workflow changed.
>
> The workflow has not changed, only the location of the repo.
Thanks for confirming.
>
> I'm afraid there's insufficient info here to say what exactly is going
> on though.
I re-executed dim setup and it seems to be working now.
Thanks.
Helen
>
> BR,
> Jani.
>
>
^ permalink raw reply [flat|nested] 32+ messages in thread