AMD-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	nouveau@lists.freedesktop.org, amd-gfx@lists.freedesktop.org
Subject: Cleanup of TTM NULL resources
Date: Thu,  7 Jul 2022 12:24:47 +0200	[thread overview]
Message-ID: <20220707102453.3633-1-christian.koenig@amd.com> (raw)

Hi guys,

sending this out once more since it was requested that the Intel CI
systems can take a run of this as well.

The last version had a couple of merge/rebase leftovers which are now
fixed as well.

Please review and/or comment,
Christian.



             reply	other threads:[~2022-07-07 10:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-07 10:24 Christian König [this message]
2022-07-07 10:24 ` [PATCH 1/6] drm/ttm: rename and cleanup ttm_bo_init_reserved Christian König
2022-07-07 10:35   ` Christian König
2022-07-07 17:24   ` [Intel-gfx] " kernel test robot
2022-07-08 13:31   ` Ruhl, Michael J
2022-07-07 10:24 ` [PATCH 2/6] drm/amdgpu: audit bo->resource usage Christian König
2022-07-08 13:34   ` [Intel-gfx] " Ruhl, Michael J
2022-07-07 10:24 ` [PATCH 3/6] drm/nouveau: " Christian König
2022-07-08 13:35   ` [Intel-gfx] " Ruhl, Michael J
2022-07-07 10:24 ` [PATCH 4/6] drm/ttm: audit bo->resource usage v2 Christian König
2022-07-08 13:48   ` [Intel-gfx] " Ruhl, Michael J
2022-07-07 10:24 ` [PATCH 5/6] drm/ttm: stop allocating dummy resources during BO creation Christian König
2022-07-08 13:54   ` Ruhl, Michael J
2022-07-09 14:31   ` [drm/ttm] b297c22b70: canonical_address#:#[##] kernel test robot
2022-07-07 10:24 ` [PATCH 6/6] drm/ttm: stop allocating a dummy resource for pipelined gutting Christian König
2022-07-08 13:56   ` Ruhl, Michael J

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=20220707102453.3633-1-christian.koenig@amd.com \
    --to=ckoenig.leichtzumerken@gmail.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=nouveau@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