On Fri, 2025-10-31 at 14:16 +0100, Christian König wrote: > When neither a release nor a wait operation is specified it is possible
Maybe call it "backend ops" instead of "operation"? > to let the dma_fence live on independent of the module who issued it. s/independent/independently > > This makes it possible to unload drivers and only wait for all their > fences to signal. > > Signed-off-by: Christian König <[email protected]> > --- > drivers/dma-buf/dma-fence.c | 16 ++++++++++++---- > include/linux/dma-fence.h | 4 ++-- > 2 files changed, 14 insertions(+), 6 deletions(-) > > diff --git a/drivers/dma-buf/dma-fence.c b/drivers/dma-buf/dma-fence.c > index ed82e8361096..cd222984e2e1 100644 > --- a/drivers/dma-buf/dma-fence.c > +++ b/drivers/dma-buf/dma-fence.c > @@ -374,6 +374,14 @@ int dma_fence_signal_timestamp_locked(struct dma_fence > *fence, > &fence->flags))) > return -EINVAL; > > + /* > + * When neither a release nor a wait operation is specified set the ops > + * pointer to NULL to allow the fence structure to become independent missing "from"
