From: Danilo Krummrich <dakr@kernel.org>
To: Tvrtko Ursulin <tvrtko.ursulin@igalia.com>
Cc: phasta@kernel.org, "Sumit Semwal" <sumit.semwal@linaro.org>,
"Gustavo Padovan" <gustavo@padovan.org>,
"Christian König" <christian.koenig@amd.com>,
linux-media@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dma-fence: Correct return of dma_fence_driver_name()
Date: Fri, 24 Oct 2025 16:36:36 +0200 [thread overview]
Message-ID: <02b7cdce-95fe-475f-a346-b41fd5615695@kernel.org> (raw)
In-Reply-To: <66f066b0-a8bb-40b2-bdd8-7cbcf114cde1@igalia.com>
On 10/24/25 4:28 PM, Tvrtko Ursulin wrote:
> On 24/10/2025 15:17, Danilo Krummrich wrote:
>> On 10/24/25 3:37 PM, Tvrtko Ursulin wrote:
>>> How about "unknown-driver", would that satisfy you?
>>
>> Honestly, the most accurate thing to say would be "fence-signaled", because
>> that's the actual condition which causes the change.
> Hm, ->get_driver_name() returning "fence-signaled" is not great, and debugfs
> output in the form of "kernel fence: fence-signaled timeline-signaled seq 1234
> signaled" feels a bit redundant. :shrug:
Indeed, what about "retired-driver"? Still implying that it's not just unknown,
but that some process has finished. But without the ambiguity of "detached-driver".
next prev parent reply other threads:[~2025-10-24 14:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-24 7:50 [PATCH] dma-fence: Correct return of dma_fence_driver_name() Philipp Stanner
2025-10-24 8:31 ` Tvrtko Ursulin
2025-10-24 10:59 ` Philipp Stanner
2025-10-24 11:31 ` Tvrtko Ursulin
2025-10-24 12:12 ` Danilo Krummrich
2025-10-24 12:40 ` Tvrtko Ursulin
2025-10-24 13:13 ` Danilo Krummrich
2025-10-24 13:37 ` Tvrtko Ursulin
2025-10-24 14:17 ` Danilo Krummrich
2025-10-24 14:28 ` Tvrtko Ursulin
2025-10-24 14:36 ` Danilo Krummrich [this message]
2025-10-24 16:06 ` Tvrtko Ursulin
2025-10-24 16:18 ` Danilo Krummrich
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=02b7cdce-95fe-475f-a346-b41fd5615695@kernel.org \
--to=dakr@kernel.org \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gustavo@padovan.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=phasta@kernel.org \
--cc=sumit.semwal@linaro.org \
--cc=tvrtko.ursulin@igalia.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