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

[Arunpravin Paneer Selvam <arunpravin.paneerselvam@amd.com>]

On 9/16/2026 3:14 PM, 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?
>
> 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?
> 3) drm-misc as default merge repo?
Hi Thomas,

I am not currently on dri-devel IRC, but I will set up an OFTC account 
and follow up with my nick shortly.

Regarding the merge process, my preference would also be option 2, i.e. 
a Reviewed-by from one of the reviewers/maintainers with no concerns 
raised within a reasonable timeframe.
For larger or more significant changes, I think a closer maintainer 
review before merging would be good.
I will also try my best to review patches on time so this rarely happens.

Using drm-misc as the default merge repository sounds good to me as well.

Thanks,
Arun.
>
> Thanks,
> Thomas