mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: "Arunpravin Paneer Selvam" <arunpravin.paneerselvam@amd.com>,
	"Christian König" <ckoenig.leichtzumerken@gmail.com>,
	christian.koenig@amd.com, ray.huang@amd.com,
	nat@pixelcluster.dev, matthew.auld@intel.com,
	matthew.brost@intel.com
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: change TTM maintainers to Natalie and Arun
Date: Thu, 17 Sep 2026 08:04:38 +0200	[thread overview]
Message-ID: <28c15950733eb5a26133858dc0d70276fb5c8d41.camel@linux.intel.com> (raw)
In-Reply-To: <d55151eb-4b81-41c7-927e-96635c1f6b7f@amd.com>

On Wed, 2026-09-16 at 16:58 +0530, Arunpravin Paneer Selvam wrote:
> 
> 
> 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,
/Thomas


> 
> Thanks,
> Arun.
> > 
> > Thanks,
> > Thomas

  reply	other threads:[~2026-09-20  7:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-15 15:48 Christian König
2026-09-15 15:51 ` Matthew Brost
2026-09-16  3:37 ` Huang Rui
2026-09-16  5:31 ` Natalie Vock
2026-09-16  8:44 ` Matthew Auld
2026-09-16  9:44 ` Thomas Hellström
2026-09-16 10:35   ` Natalie Vock
2026-09-16 10:42     ` Thomas Hellström
2026-09-16 11:28   ` Arunpravin Paneer Selvam
2026-09-17  6:04     ` Thomas Hellström [this message]
2026-09-16 10:17 ` Arunpravin Paneer Selvam

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=28c15950733eb5a26133858dc0d70276fb5c8d41.camel@linux.intel.com \
    --to=thomas.hellstrom@linux.intel.com \
    --cc=arunpravin.paneerselvam@amd.com \
    --cc=christian.koenig@amd.com \
    --cc=ckoenig.leichtzumerken@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew.auld@intel.com \
    --cc=matthew.brost@intel.com \
    --cc=nat@pixelcluster.dev \
    --cc=ray.huang@amd.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®