Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sanjay Yadav <sanjay.kumar.yadav@intel.com>
To: dri-devel@lists.freedesktop.org
Cc: intel-xe@lists.freedesktop.org,
	"Christian König" <christian.koenig@amd.com>,
	"Arunpravin Paneer Selvam" <Arunpravin.PaneerSelvam@amd.com>,
	"Matthew Auld" <matthew.auld@intel.com>
Subject: [PATCH 0/2] drm/buddy: Documentation and internal helper cleanup
Date: Wed,  4 Feb 2026 16:13:44 +0530	[thread overview]
Message-ID: <20260204104345.1980047-4-sanjay.kumar.yadav@intel.com> (raw)

This series improves the DRM buddy allocator by adding missing
documentation and cleaning up internal helpers.

It adds kernel-doc for the allocator structures and flags, covering
drm_buddy, drm_buddy_block, and the allocation flags (RANGE, TOPDOWN,
CONTIGUOUS, CLEAR, TRIM_DISABLE) to make the allocator’s design and usage
clearer for readers and contributors.

It also reduces the header surface by moving internal helpers from
drm_buddy.h into drm_buddy.c as static functions, since they have no
external users, and removes drm_get_buddy(), an unused exported wrapper
around the internal __get_buddy() helper. This clarifies the intended API
and avoids exporting unused symbols.

No functional changes.

Cc: Christian König <christian.koenig@amd.com>
Cc: Arunpravin Paneer Selvam <Arunpravin.PaneerSelvam@amd.com>
Suggested-by: Matthew Auld <matthew.auld@intel.com>

Sanjay Yadav (2):
  drm/buddy: Move internal helpers to drm_buddy.c
  drm/buddy: Add kernel-doc for allocator structures and flags

 drivers/gpu/drm/drm_buddy.c |  41 ++++++----
 include/drm/drm_buddy.h     | 149 ++++++++++++++++++++++++------------
 2 files changed, 126 insertions(+), 64 deletions(-)

-- 
2.52.0


             reply	other threads:[~2026-02-04 10:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-04 10:43 Sanjay Yadav [this message]
2026-02-04 10:43 ` [PATCH 1/2] drm/buddy: Move internal helpers to drm_buddy.c Sanjay Yadav
2026-02-06  8:27   ` Paneer Selvam, Arunpravin
2026-02-04 10:43 ` [PATCH 2/2] drm/buddy: Add kernel-doc for allocator structures and flags Sanjay Yadav
2026-02-06  8:39   ` Paneer Selvam, Arunpravin
2026-02-04 10:54 ` ✓ CI.KUnit: success for drm/buddy: Documentation and internal helper cleanup Patchwork
2026-02-04 11:53 ` ✗ Xe.CI.BAT: failure " Patchwork
2026-02-04 22:03 ` ✗ Xe.CI.FULL: " Patchwork
2026-02-04 22:32 ` ✓ CI.KUnit: success for drm/buddy: Documentation and internal helper cleanup (rev2) Patchwork
2026-02-04 23:24 ` ✓ Xe.CI.BAT: " Patchwork
2026-02-05 13:53 ` ✗ Xe.CI.FULL: failure " Patchwork

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=20260204104345.1980047-4-sanjay.kumar.yadav@intel.com \
    --to=sanjay.kumar.yadav@intel.com \
    --cc=Arunpravin.PaneerSelvam@amd.com \
    --cc=christian.koenig@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.auld@intel.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