From: "Christian König" <christian.koenig@amd.com>
To: Matthew Auld <matthew.auld@intel.com>,
Arunpravin Paneer Selvam <Arunpravin.PaneerSelvam@amd.com>,
dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
intel-xe@lists.freedesktop.org, amd-gfx@lists.freedesktop.org
Cc: alexander.deucher@amd.com, airlied@gmail.com, simona@ffwll.ch
Subject: Re: [PATCH] MAINTAINERS: drm: add maintainers for DRM buddy allocator
Date: Mon, 12 Jan 2026 11:08:42 +0100 [thread overview]
Message-ID: <7d1f9c33-1d5e-4b8a-aefa-8180efc2009b@amd.com> (raw)
In-Reply-To: <4d76d9f8-0cf1-46b0-bced-8d6e71ff322b@intel.com>
On 1/12/26 10:43, Matthew Auld wrote:
> On 12/01/2026 07:24, Arunpravin Paneer Selvam wrote:
>> The DRM buddy allocator is a shared DRM memory management
>> component used by multiple DRM drivers.
>>
>> Matthew Auld and Arun Pravin have been actively involved in
>> maintaining this code, including patch review and functional
>> changes.
>>
>> Add a dedicated MAINTAINERS entry to reflect the current
>> maintainership.
>>
>> Signed-off-by: Arunpravin Paneer Selvam <Arunpravin.PaneerSelvam@amd.com>
>> ---
>> MAINTAINERS | 10 ++++++++++
>> 1 file changed, 10 insertions(+)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index 6169bd4d7bac..3cd69f6905ae 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -8780,6 +8780,16 @@ T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
>> F: drivers/gpu/drm/ttm/
>> F: include/drm/ttm/
>> +DRM BUDDY ALLOCATOR
>> +M: Matthew Auld <matthew.auld@intel.com>
>> +M: Arun Pravin <arunpravin.paneerselvam@amd.com>
>> +R: Christian Koenig <christian.koenig@amd.com>
>> +L: dri-devel@lists.freedesktop.org
>> +S: Maintained
>> +T: git https://gitlab.freedesktop.org/drm/misc/kernel.git
>> +F: drivers/gpu/drm/drm_buddy.c
>> +F: include/drm/drm_buddy.h
>
> I guess we should also add:
>
> drivers/gpu/drm/tests/drm_buddy_test.c
> > ?
Good point, completely agree.
>
> Acked-by: Matthew Auld <matthew.auld@intel.com>
Acked-by: Christian König <christian.koenig@amd.com>
>
>> +
>> DRM AUTOMATED TESTING
>> M: Helen Koike <helen.fornazier@gmail.com>
>> M: Vignesh Raman <vignesh.raman@collabora.com>
>
prev parent reply other threads:[~2026-01-12 10:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-12 7:24 [PATCH] MAINTAINERS: drm: add maintainers for DRM buddy allocator Arunpravin Paneer Selvam
2026-01-12 9:43 ` Matthew Auld
2026-01-12 10:08 ` Christian König [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7d1f9c33-1d5e-4b8a-aefa-8180efc2009b@amd.com \
--to=christian.koenig@amd.com \
--cc=Arunpravin.PaneerSelvam@amd.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.auld@intel.com \
--cc=simona@ffwll.ch \
/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