From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: dri-devel@lists.freedesktop.org
Cc: daniel@ffwll.ch, linux-media@vger.kernel.org,
linaro-mm-sig@lists.linaro.org
Subject: Harden the dma-fence documentation a bit more
Date: Wed, 1 Sep 2021 14:02:38 +0200 [thread overview]
Message-ID: <20210901120240.7339-1-christian.koenig@amd.com> (raw)
Hi guys,
while it is in most cases technically possible to not have a reference to the dma_fence when adding a callback it is usually a good idea to make sure to always have a reference anyway.
Otherwise we can indeed see cases where this doesn't really work as intended like for example in the now fixed EPOLL code.
Regards,
Christian.
next reply other threads:[~2021-09-01 12:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-01 12:02 Christian König [this message]
2021-09-01 12:02 ` [PATCH 1/2] dma-buf: clarify dma_fence_ops->wait documentation Christian König
2021-09-02 14:37 ` Daniel Vetter
2021-09-01 12:02 ` [PATCH 2/2] dma-buf: clarify dma_fence_add_callback documentation Christian König
2021-09-02 14:42 ` Daniel Vetter
2021-09-03 8:22 ` 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=20210901120240.7339-1-christian.koenig@amd.com \
--to=ckoenig.leichtzumerken@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-media@vger.kernel.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