From: sashiko-bot@kernel.org
To: "Philipp Stanner" <phasta@kernel.org>
Cc: virtualization@lists.linux.dev, linux-usb@vger.kernel.org,
"Michael S. Tsirkin" <mst@redhat.com>,
"Eugenio Perez" <eperezma@redhat.com>
Subject: Re: [PATCH 1/3] dma-buf: dma-fence: Add flags parameter to dma_fence_init()
Date: Thu, 05 Nov 2026 11:54:53 +0000 [thread overview]
Message-ID: <sashiko-outbox-198976@kernel.org> (raw)
In-Reply-To: <20261105113529.1989375-3-phasta@kernel.org>
> Currently, there are two init functions for dma_fence, dma_fence_init()
> and dma_fence_init64().
>
> Since more future user options for dma_fence initialization would
> require distinct init functions, too, it is better to do this in a
> unified way.
>
> Add a flags field to dma_fence_init(). Adjust all affected drivers,
> preserving the old behavior.
>
> Support the SEQNO64 flag, and add a check-function so that the user only
> sets valid bits.
>
> Signed-off-by: Philipp Stanner <phasta@kernel.org>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261105113529.1989375-2-phasta@kernel.org?part=1
next prev parent reply other threads:[~2026-11-05 11:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 11:35 [PATCH 0/3] dma-buf: dma-fence: Remove dma_fence_init64() Philipp Stanner
2026-11-05 11:35 ` [PATCH 1/3] dma-buf: dma-fence: Add flags parameter to dma_fence_init() Philipp Stanner
2026-11-05 11:54 ` sashiko-bot [this message]
2026-11-05 12:06 ` Tvrtko Ursulin
2026-11-05 12:35 ` Christian König
2026-11-05 12:48 ` Philipp Stanner
2026-11-05 14:23 ` Christian König
2026-11-05 12:51 ` Tvrtko Ursulin
2026-11-05 13:24 ` Philipp Stanner
2026-11-05 11:35 ` [PATCH 2/3] dma-buf: Port users of dma_fence_init64() Philipp Stanner
2026-11-05 11:49 ` sashiko-bot
2026-11-05 11:35 ` [PATCH 3/3] dma-buf: dma-fence: Remove dma_fence_init64() Philipp Stanner
2026-11-05 11:43 ` sashiko-bot
2026-11-05 14:14 ` ✗ CI.checkpatch: warning for " Patchwork
2026-11-05 14:16 ` ✓ CI.KUnit: success " Patchwork
2026-11-05 14:53 ` ✓ Xe.CI.BAT: " Patchwork
2026-11-05 16:32 ` [PATCH 0/3] " Timur Kristóf
2026-11-05 17:58 ` ✗ i915.CI.BAT: failure for " Patchwork
2026-11-06 11:48 ` ✓ Xe.CI.FULL: success " Patchwork
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=sashiko-outbox-198976@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=eperezma@redhat.com \
--cc=linux-usb@vger.kernel.org \
--cc=mst@redhat.com \
--cc=phasta@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=virtualization@lists.linux.dev \
/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.