Re: [PATCH 2/3] dma-fence: use default wait function for mock fences

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: [PATCH 2/3] dma-fence: use default wait function for mock fences
From: Chris Wilson <chris@xxxxxxxxxxxxxxxxxx>
Date: Mon, 11 May 2020 10:41:03 +0100
Cc: Daniel Vetter <daniel.vetter@xxxxxxxx>, Intel Graphics Development <intel-gfx@xxxxxxxxxxxxxxxxxxxxx>, DRI Development <dri-devel@xxxxxxxxxxxxxxxxxxxxx>, linaro-mm-sig@xxxxxxxxxxxxxxxx, Daniel Vetter <daniel.vetter@xxxxxxxxx>, linux-media@xxxxxxxxxxxxxxx
In-reply-to: <20200511091142.208787-2-daniel.vetter@ffwll.ch>
References: <20200511091142.208787-1-daniel.vetter@ffwll.ch> <20200511091142.208787-2-daniel.vetter@ffwll.ch>
User-agent: alot/0.8.1

Quoting Daniel Vetter (2020-05-11 10:11:41)
> No need to micro-optmize when we're waiting in a mocked object ...

It's setting up the expected return values for the test.
-Chris
_______________________________________________
dri-devel mailing list
dri-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/dri-devel

Follow-Ups:
- Re: [PATCH 2/3] dma-fence: use default wait function for mock fences
  - From: Daniel Vetter

References:
- [PATCH 1/3] drm/writeback: don't set fence->ops to default
  - From: Daniel Vetter
- [PATCH 2/3] dma-fence: use default wait function for mock fences
  - From: Daniel Vetter

Prev by Date: Re: [PATCH 3/3] misc/habalabs: don't set default fence_ops->wait
Next by Date: Re: [PATCH 3/3] misc/habalabs: don't set default fence_ops->wait
Previous by thread: [PATCH 2/3] dma-fence: use default wait function for mock fences
Next by thread: Re: [PATCH 2/3] dma-fence: use default wait function for mock fences
Index(es):
- Date
- Thread

[Index of Archives] [Linux DRI Users] [Linux Intel Graphics] [Linux USB Devel] [Video for Linux] [Linux Audio Users] [Yosemite News] [Linux Kernel] [Linux SCSI] [XFree86] [Linux USB Devel] [Video for Linux] [Linux Audio Users] [Linux Kernel] [Linux SCSI] [XFree86]