Re: [PATCH] MAINTAINERS: change TTM maintainers to Natalie and Arun

["Thomas Hellström" <thomas.hellstrom@linux.intel.com>]

On Wed, 2026-09-16 at 12:35 +0200, Natalie Vock wrote:
> Hi,
> 
> On 9/16/26 11:44, Thomas Hellström wrote:
> > On Tue, 2026-09-15 at 17:48 +0200, Christian König wrote:
> > > The blunt reality is that I don't have time to look into patches
> > > or
> > > bugs
> > > any more as it would be necessary. The same counts for Ray.
> > > 
> > > Natalie has been working on the dmem cgroup patches for TTM and
> > > agreed
> > > to take over looking more into TTM.
> > > 
> > > Arun is working in my team and already maintaining AMDs VRAM
> > > backend
> > > for
> > > TTM and the underlying buddy allocator.
> > > 
> > > Add Thomas as reviewer as well, better to have more eyes on that
> > > component.
> > > 
> > > Signed-off-by: Christian König <christian.koenig@amd.com>
> > > ---
> > >   MAINTAINERS | 5 +++--
> > >   1 file changed, 3 insertions(+), 2 deletions(-)
> > > 
> > > diff --git a/MAINTAINERS b/MAINTAINERS
> > > index 5b5a4e4b35cf..b6e58a138501 100644
> > > --- a/MAINTAINERS
> > > +++ b/MAINTAINERS
> > > @@ -9140,10 +9140,11 @@
> > > 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>
> > > +M:	Natalie Vock <nat@pixelcluster.dev>
> > > +M:	Arun Pravin <arunpravin.paneerselvam@amd.com>
> > >   R:	Matthew Auld <matthew.auld@intel.com>
> > >   R:	Matthew Brost <matthew.brost@intel.com>
> > > +R:	Thomas Hellström <thomas.hellstrom@linux.intel.com>
> > >   L:	dri-devel@lists.freedesktop.org
> > >   S:	Maintained
> > >   T:	git https://gitlab.freedesktop.org/drm/misc/kernel.git
> > 
> > Acked-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
> > 
> > @Natalie, @Arun Do you have a presence on dri-devel IRC? If so,
> > Nicks?
> 
> Yes, I have the nick "pixelcluster".
> 
> > 
> > Also what is your stance on merging pages to TTM?
> > 1) Requiring an explicit maintainer ack, or
> > 2) an R-B from one of the reviewers/maintainers and no concerns
> > raised
> > within reasonable time?
> 
> I think my preference would more or less be 2). That is, if for some
> reason no maintainer answers, after some time the patches should be
> ok
> to merge (but if a maintainer does explicitly ack/R-b the patch it
> can
> be merged sooner). I'll try my best to not leave patches unanswered
> so
> hopefully 2) stays a rarity :)
> 
> > 3) drm-misc as default merge repo?
> 
> Sure, why not? Basically like it's been so far as well, right? It
> didn't
> seem to me like the patch volume for TTM is particularly large at
> least
> so far, so something like a separate branch might not be worth the
> hassle.

Great. Thanks. Reason for the last question was more that if we want to
merge TTM patches outside of the default branch if they are required
for a driver feature, and then we always ask for ack to merge on a
different branch / repo. If we have an agreed default we typically
don't ask for a separate merge ack on that one.

/Thomas

> 
> Best,
> Natalie