public inbox for drm-ai-reviews@public-inbox.freedesktop.org
 help / color / mirror / Atom feed
From: Joel Fernandes <joelagnelf@nvidia.com>
To: Lukas Bulwahn <lukas.bulwahn@redhat.com>
Cc: Dave Airlie <airlied@redhat.com>,
	Matthew Auld <matthew.auld@intel.com>,
	Arun Pravin <arunpravin.paneerselvam@amd.com>,
	Christian Koenig <christian.koenig@amd.com>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Maxime Ripard <mripard@kernel.org>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
	dri-devel@lists.freedesktop.org, kernel-janitors@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: adjust file entry in GPU BUDDY ALLOCATOR
Date: Wed, 11 Mar 2026 02:25:58 -0400	[thread overview]
Message-ID: <1773210317.4fdee550f80fd797@nvidia.com> (raw)
In-Reply-To: <20260311043314.265627-1-lukas.bulwahn@redhat.com>

On Wed, 11 Mar 2026, Lukas Bulwahn wrote:
> The commit 4a9671a03f2b ("gpu: Move DRM buddy allocator one level up (part
> one)") and commit ba110db8e1bc ("gpu: Move DRM buddy allocator one level up
> (part two)") split the majority of the file drivers/gpu/drm/drm_buddy.c
> into drivers/gpu/buddy.c, with some pieces remaining in the original
> location drivers/gpu/drm/drm_buddy.c.
>
> The commits also adjust the file entries in the GPU BUDDY ALLOCATOR
> section, but as part of that, change the file entry to the non-existing
> file drivers/gpu/drm_buddy.c instead of keeping the reference to the
> existing file drivers/gpu/drm/drm_buddy.c.
>
> Make the file entry in GPU BUDDY ALLOCATOR refer to the intended existing
> file. While at it, order the file entries in this section alphabetically.

Reviewed-by: Joel Fernandes <joelagnelf@nvidia.com>

-- 
Joel Fernandes

  reply	other threads:[~2026-03-11  6:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-11  4:33 [PATCH] MAINTAINERS: adjust file entry in GPU BUDDY ALLOCATOR Lukas Bulwahn
2026-03-11  6:25 ` Joel Fernandes [this message]
2026-03-11  6:31 ` Arunpravin Paneer Selvam
2026-03-11  7:58 ` Maxime Ripard
2026-03-11 21:19 ` Claude review: " Claude Code Review Bot
2026-03-11 21:19 ` Claude Code Review Bot

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=1773210317.4fdee550f80fd797@nvidia.com \
    --to=joelagnelf@nvidia.com \
    --cc=airlied@gmail.com \
    --cc=airlied@redhat.com \
    --cc=arunpravin.paneerselvam@amd.com \
    --cc=christian.koenig@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukas.bulwahn@redhat.com \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=matthew.auld@intel.com \
    --cc=mripard@kernel.org \
    --cc=simona@ffwll.ch \
    --cc=tzimmermann@suse.de \
    /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