Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: dri-devel@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>
Subject: [PATCH 0/2] Add DRM-managed drm_mm_init()
Date: Fri, 24 May 2024 15:35:16 +0200	[thread overview]
Message-ID: <20240524133518.976-1-michal.wajdeczko@intel.com> (raw)

Add drmm_mm_init(), a helper that provides managed allocator cleanup,
and start using it in the Xe driver.

Michal Wajdeczko (2):
  drm: Add DRM-managed drm_mm_init()
  drm/xe: Use drm_device managed mutex/mm init helpers in GGTT

 drivers/gpu/drm/drm_managed.c | 27 +++++++++++++++++++++++++++
 drivers/gpu/drm/xe/xe_ggtt.c  | 23 +++++++++++------------
 include/drm/drm_managed.h     |  3 +++
 3 files changed, 41 insertions(+), 12 deletions(-)

-- 
2.43.0


             reply	other threads:[~2024-05-24 13:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-24 13:35 Michal Wajdeczko [this message]
2024-05-24 13:35 ` [PATCH 1/2] drm: Add DRM-managed drm_mm_init() Michal Wajdeczko
2024-06-06 17:27   ` Rodrigo Vivi
2024-05-24 13:35 ` [PATCH 2/2] drm/xe: Use drm_device managed mutex/mm init helpers in GGTT Michal Wajdeczko
2024-06-06 17:25   ` Rodrigo Vivi
2024-06-06 18:33     ` Michal Wajdeczko
2024-05-24 13:41 ` ✓ CI.Patch_applied: success for Add DRM-managed drm_mm_init() Patchwork
2024-05-24 13:42 ` ✓ CI.checkpatch: " Patchwork
2024-05-24 13:43 ` ✓ CI.KUnit: " Patchwork
2024-05-24 13:54 ` ✓ CI.Build: " Patchwork
2024-05-24 13:57 ` ✓ CI.Hooks: " Patchwork
2024-05-24 13:58 ` ✗ CI.checksparse: warning " Patchwork
2024-05-24 14:28 ` ✗ CI.BAT: failure " Patchwork
2024-05-24 17:25   ` Michal Wajdeczko
2024-05-27 11:27 ` ✗ CI.FULL: " 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=20240524133518.976-1-michal.wajdeczko@intel.com \
    --to=michal.wajdeczko@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    /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