From: Philipp Stanner <phasta@kernel.org>
To: "Sumit Semwal" <sumit.semwal@linaro.org>,
"Christian König" <christian.koenig@amd.com>,
"Yury Norov" <yury.norov@gmail.com>,
"Rasmus Villemoes" <linux@rasmusvillemoes.dk>,
"Arnd Bergmann" <arnd@arndb.de>,
"Tvrtko Ursulin" <tvrtko.ursulin@igalia.com>,
"Danilo Krummrich" <dakr@kernel.org>,
"Gary Guo" <gary@garyguo.net>,
"Paul E . McKenney" <paulmck@kernel.org>
Cc: linux-media@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
Philipp Stanner <phasta@kernel.org>
Subject: [PATCH 0/2] dma-fence: Order is-signaled-bit
Date: Wed, 21 Oct 2026 11:55:11 +0200 [thread overview]
Message-ID: <20261021095512.1345191-2-phasta@kernel.org> (raw)
Changes in v2:
- Add a set_bit_release() function for proper ordering and use it.
Based on the DRM branch drm-misc-next
Philipp Stanner (2):
asm-generic/bitops: Add set_bit_release()
dma-buf/dma-fence: Order setting of the signaled-bit properly
drivers/dma-buf/dma-fence.c | 11 +++++++++--
include/asm-generic/bitops/instrumented-atomic.h | 14 ++++++++++++++
include/linux/dma-fence.h | 6 +++++-
3 files changed, 28 insertions(+), 3 deletions(-)
base-commit: 1ecab8b0bad393750c60cc3819ce9c256595463c
--
2.56.0
next reply other threads:[~2026-10-21 9:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 9:55 Philipp Stanner [this message]
2026-10-21 9:55 ` [PATCH 1/2] asm-generic/bitops: Add set_bit_release() Philipp Stanner
2026-10-21 10:06 ` sashiko-bot
2026-10-21 11:33 ` Arnd Bergmann
2026-10-21 11:54 ` Gary Guo
2026-10-21 12:15 ` Arnd Bergmann
2026-10-21 12:06 ` Gary Guo
2026-10-21 12:17 ` Philipp Stanner
2026-10-21 12:24 ` Gary Guo
2026-10-21 13:22 ` Philipp Stanner
2026-10-21 9:55 ` [PATCH 2/2] dma-buf/dma-fence: Order setting of the signaled-bit properly Philipp Stanner
2026-10-21 10:16 ` sashiko-bot
2026-10-21 13:47 ` Christian König
2026-10-21 14:52 ` Philipp Stanner
2026-10-21 15:04 ` Christian König
2026-10-26 1:34 ` kernel test robot
2026-10-26 7:48 ` kernel test robot
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=20261021095512.1345191-2-phasta@kernel.org \
--to=phasta@kernel.org \
--cc=arnd@arndb.de \
--cc=christian.koenig@amd.com \
--cc=dakr@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=gary@garyguo.net \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=paulmck@kernel.org \
--cc=sumit.semwal@linaro.org \
--cc=tvrtko.ursulin@igalia.com \
--cc=yury.norov@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.