From: "Christian König" <christian.koenig@amd.com>
To: Matthew Brost <matthew.brost@intel.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: Mon, 7 Jul 2025 12:59:14 +0200 [thread overview]
Message-ID: <c1759ff2-e920-4cca-8dc2-e7de1abadf83@amd.com> (raw)
In-Reply-To: <aGVbCnLV9fWNwPnS@lstrano-desk.jf.intel.com>
On 02.07.25 18:15, Matthew Brost wrote:
> 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?
Yeah, that works for me.
But I would rather like to get the first patch in if possible since that is just a simple rename.
Christian.
>
> Matt
>
>> Regards,
>> Christian.
>>
>>
prev parent reply other threads:[~2025-07-07 10:59 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 ` Switching TTM over to GEM refcounts v2 Matthew Brost
2025-07-07 10:59 ` Christian König [this message]
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=c1759ff2-e920-4cca-8dc2-e7de1abadf83@amd.com \
--to=christian.koenig@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.brost@intel.com \
--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