Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Brost <matthew.brost@intel.com>
To: "Christian König" <ckoenig.leichtzumerken@gmail.com>
Cc: <thomas.hellstrom@linux.intel.com>,
	<intel-xe@lists.freedesktop.org>,
	<dri-devel@lists.freedesktop.org>,
	<amd-gfx@lists.freedesktop.org>
Subject: Re: Switching TTM over to GEM refcounts v2
Date: Wed, 2 Jul 2025 09:15:06 -0700	[thread overview]
Message-ID: <aGVbCnLV9fWNwPnS@lstrano-desk.jf.intel.com> (raw)
In-Reply-To: <20250702110028.2521-1-christian.koenig@amd.com>

On Wed, Jul 02, 2025 at 01:00:26PM +0200, Christian König wrote:
> Hi everyone,
> 
> v2 of this patch set. I've either pushed or removed the other
> patches from v1, so only two remain.
> 
> Pretty straight forward conversation and shouldn't result in any visible
> technical difference.
> 
> Please review and/or comment.
> 

I'll take a look but heads up Thomas is out until 7/21. I know he did
some concerns on v1, so might need to wait for him to get back?

Matt 

> Regards,
> Christian.
> 
> 

  parent reply	other threads:[~2025-07-02 16:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-02 11:00 Switching TTM over to GEM refcounts v2 Christian König
2025-07-02 11:00 ` [PATCH 1/2] drm/ttm: rename ttm_bo_put to _fini Christian König
2025-07-02 22:01   ` Matthew Brost
2025-07-07 12:38     ` Christian König
2025-07-07 16:25       ` Matthew Brost
2025-07-07 18:16         ` Christian König
2025-07-02 11:00 ` [PATCH 2/2] drm/ttm: replace TTMs refcount with the DRM refcount v2 Christian König
2025-07-02 12:08 ` ✗ CI.checkpatch: warning for series starting with [1/2] drm/ttm: rename ttm_bo_put to _fini Patchwork
2025-07-02 12:09 ` ✗ CI.KUnit: failure " Patchwork
2025-07-02 16:15 ` Matthew Brost [this message]
2025-07-07 10:59   ` Switching TTM over to GEM refcounts v2 Christian König

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=aGVbCnLV9fWNwPnS@lstrano-desk.jf.intel.com \
    --to=matthew.brost@intel.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=ckoenig.leichtzumerken@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=thomas.hellstrom@linux.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