diff options
| author | Philipp Stanner <phasta@kernel.org> | 2025-12-01 11:50:07 +0100 |
|---|---|---|
| committer | Philipp Stanner <phasta@kernel.org> | 2025-12-04 15:03:40 +0100 |
| commit | 06bc18e0def7d926265480faa555bf0b67a35a90 (patch) | |
| tree | 326696ff6e3caf24519459f33d04e22425522c91 /tools/perf/lib/Documentation/tutorial/git@git.tavy.me:linux.git | |
| parent | c891b99d25ddbb6b8167f9bdb904d4abc5a53b6b (diff) | |
amd/amdkfd: Use dma_fence_check_and_signal()
amdkfd is one of the few users which relies on the return code of
dma_fence_signal(), which, so far, informs the caller whether the fence
had already been signaled.
As there are barely any users, dma_fence signaling functions shall get
the return value void. To do so, the few users must be ported to a
function which preserves the old behavior.
Replace the call to dma_fence_signal() with one to
dma_fence_check_and_signal().
Suggested-by: Christian König <christian.koenig@amd.com>
Reviewed-by: Christian König <christian.koenig@amd.com>
Reviewed-by: Felix Kuehling <felix.kuehling@amd.com>
Signed-off-by: Philipp Stanner <phasta@kernel.org>
Link: https://patch.msgid.link/20251201105011.19386-5-phasta@kernel.org
Diffstat (limited to 'tools/perf/lib/Documentation/tutorial/git@git.tavy.me:linux.git')
0 files changed, 0 insertions, 0 deletions
