From: Tvrtko Ursulin <tursulin@ursulin.net>
To: Akash Goel <akash.goel@arm.com>,
sumit.semwal@linaro.org, gustavo@padovan.org,
christian.koenig@amd.com
Cc: linux-media@vger.kernel.org, dri-devel@lists.freedesktop.org,
linaro-mm-sig@lists.linaro.org, linux-kernel@vger.kernel.org,
nd@arm.com, stable@vger.kernel.org
Subject: Re: [PATCH] dma-fence: Fix safe access wrapper to call timeline name method
Date: Tue, 21 Oct 2025 19:36:44 +0100 [thread overview]
Message-ID: <d9c16e9e-8321-41fe-9112-e754445d8bb0@ursulin.net> (raw)
In-Reply-To: <20251021160951.1415603-1-akash.goel@arm.com>
On 21/10/2025 17:09, Akash Goel wrote:
> This commit fixes the wrapper function dma_fence_timeline_name(), that
> was added for safe access, to actually call the timeline name method of
> dma_fence_ops.
>
> Cc: <stable@vger.kernel.org> # v6.17+
> Signed-off-by: Akash Goel <akash.goel@arm.com>
Fixes: 506aa8b02a8d ("dma-fence: Add safe access helpers and document
the rules")
Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@igalia.com>
Apologies for the copy and paste snafu.
Regards,
Tvrtko
> ---
> drivers/dma-buf/dma-fence.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/dma-buf/dma-fence.c b/drivers/dma-buf/dma-fence.c
> index 3f78c56b58dc..39e6f93dc310 100644
> --- a/drivers/dma-buf/dma-fence.c
> +++ b/drivers/dma-buf/dma-fence.c
> @@ -1141,7 +1141,7 @@ const char __rcu *dma_fence_timeline_name(struct dma_fence *fence)
> "RCU protection is required for safe access to returned string");
>
> if (!test_bit(DMA_FENCE_FLAG_SIGNALED_BIT, &fence->flags))
> - return fence->ops->get_driver_name(fence);
> + return fence->ops->get_timeline_name(fence);
> else
> return "signaled-timeline";
> }
next prev parent reply other threads:[~2025-10-21 18:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-21 16:09 Akash Goel
2025-10-21 18:36 ` Tvrtko Ursulin [this message]
2025-10-27 10:27 ` 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=d9c16e9e-8321-41fe-9112-e754445d8bb0@ursulin.net \
--to=tursulin@ursulin.net \
--cc=akash.goel@arm.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gustavo@padovan.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=nd@arm.com \
--cc=stable@vger.kernel.org \
--cc=sumit.semwal@linaro.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
all inboxes | Powered by JetHome®