From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>,
DRI Development <dri-devel@lists.freedesktop.org>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 00/17] dma-fence doc polish and small cleanup
Date: Sun, 29 Apr 2018 09:15:46 +0200 [thread overview]
Message-ID: <0a579e7e-3432-a8b3-3bb5-f9a89cb212b2@gmail.com> (raw)
In-Reply-To: <20180427061724.28497-1-daniel.vetter@ffwll.ch>
Patches #1-#5 in this series are Reviewed-by: Christian König
<christian.koenig@amd.com>
Regards,
Christian.
Am 27.04.2018 um 08:17 schrieb Daniel Vetter:
> Hi all,
>
> Somewhat motivated by me looking at the v3d patch I went and dug around
> in the dma-fence code a bit. Result was a bit of doc polish and making a
> bunch of callbacks optional for cases where most implementations wanted
> the same default behaviour.
>
> Comments, testing, feedback very much welcome.
>
> Thanks, Daniel
>
> Daniel Vetter (17):
> dma-fence: Some kerneldoc polish for dma-fence.h
> dma-fence: remove fill_driver_data callback
> dma-fence: Make ->enable_signaling optional
> dma-fence: Allow wait_any_timeout for all fences
> dma-fence: Make ->wait callback optional
> drm/amdgpu: Remove unecessary dma_fence_ops
> drm: Remove unecessary dma_fence_ops
> drm/etnaviv: Remove unecessary dma_fence_ops
> drm/i915: Remove unecessary dma_fence_ops
> drm/msm: Remove unecessary dma_fence_ops
> drm/nouveau: Remove unecessary dma_fence_ops
> drm/qxl: Remove unecessary dma_fence_ops
> drm/radeon: Remove custom dma_fence_ops->wait implementation
> drm/vc4: Remove unecessary dma_fence_ops
> drm/vgem: Remove unecessary dma_fence_ops
> drm/virtio: Remove unecessary dma_fence_ops
> dma-fence: Polish kernel-doc for dma-fence.c
>
> Documentation/driver-api/dma-buf.rst | 6 +
> drivers/dma-buf/dma-fence-array.c | 1 -
> drivers/dma-buf/dma-fence.c | 163 ++++++++----
> drivers/dma-buf/sw_sync.c | 1 -
> .../gpu/drm/amd/amdgpu/amdgpu_amdkfd_fence.c | 2 -
> drivers/gpu/drm/amd/amdgpu/amdgpu_fence.c | 1 -
> drivers/gpu/drm/drm_crtc.c | 7 -
> drivers/gpu/drm/drm_syncobj.c | 1 -
> drivers/gpu/drm/etnaviv/etnaviv_gpu.c | 7 -
> drivers/gpu/drm/i915/i915_gem_clflush.c | 7 -
> .../gpu/drm/i915/selftests/i915_sw_fence.c | 7 -
> drivers/gpu/drm/msm/msm_fence.c | 7 -
> drivers/gpu/drm/nouveau/nouveau_fence.c | 1 -
> drivers/gpu/drm/qxl/qxl_release.c | 7 -
> drivers/gpu/drm/radeon/radeon_fence.c | 63 -----
> drivers/gpu/drm/scheduler/sched_fence.c | 11 -
> drivers/gpu/drm/vc4/vc4_fence.c | 7 -
> drivers/gpu/drm/vgem/vgem_fence.c | 14 --
> drivers/gpu/drm/virtio/virtgpu_fence.c | 7 -
> include/linux/dma-fence.h | 231 +++++++++++-------
> 20 files changed, 267 insertions(+), 284 deletions(-)
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2018-04-29 7:15 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-27 6:17 [PATCH 00/17] dma-fence doc polish and small cleanup Daniel Vetter
2018-04-27 6:17 ` [PATCH 01/17] dma-fence: Some kerneldoc polish for dma-fence.h Daniel Vetter
2018-04-30 17:49 ` Eric Anholt
2018-05-02 7:38 ` [Intel-gfx] " Daniel Vetter
2018-04-27 6:17 ` [PATCH 02/17] dma-fence: remove fill_driver_data callback Daniel Vetter
2018-04-30 17:49 ` Eric Anholt
2018-05-02 8:23 ` [PATCH] " Daniel Vetter
2018-05-02 16:57 ` Eric Anholt
2018-04-27 6:17 ` [PATCH 03/17] dma-fence: Make ->enable_signaling optional Daniel Vetter
2018-04-27 6:17 ` [PATCH 04/17] dma-fence: Allow wait_any_timeout for all fences Daniel Vetter
2018-04-29 7:11 ` Christian König
2018-04-30 15:35 ` Daniel Vetter
2018-04-27 6:17 ` [PATCH 05/17] dma-fence: Make ->wait callback optional Daniel Vetter
2018-04-27 6:17 ` [PATCH 06/17] drm/amdgpu: Remove unecessary dma_fence_ops Daniel Vetter
2018-04-29 7:12 ` Christian König
2018-04-27 6:17 ` [PATCH 07/17] drm: " Daniel Vetter
2018-04-30 17:51 ` Eric Anholt
2018-04-27 6:17 ` [PATCH 08/17] drm/etnaviv: " Daniel Vetter
2018-05-03 13:43 ` Lucas Stach
2018-04-27 6:17 ` [PATCH 09/17] drm/i915: " Daniel Vetter
[not found] ` <20180427061724.28497-1-daniel.vetter-/w4YWyX8dFk@public.gmane.org>
2018-04-27 6:17 ` [PATCH 10/17] drm/msm: " Daniel Vetter
2018-04-27 6:17 ` [PATCH 11/17] drm/nouveau: " Daniel Vetter
2018-04-27 6:17 ` [PATCH 12/17] drm/qxl: " Daniel Vetter
2018-04-30 17:53 ` Eric Anholt
2018-05-02 8:23 ` [PATCH] " Daniel Vetter
2018-04-27 6:17 ` [PATCH 13/17] drm/radeon: Remove custom dma_fence_ops->wait implementation Daniel Vetter
2018-04-29 7:08 ` Christian König
2018-04-30 15:38 ` Daniel Vetter
[not found] ` <20180430153854.GR12521-dv86pmgwkMBes7Z6vYuT8azUEOm+Xw19@public.gmane.org>
2018-04-30 18:26 ` Christian König
[not found] ` <ba53bdbd-3311-5836-4529-5374ccf6584a-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-04-30 19:35 ` Daniel Vetter
2018-04-27 6:17 ` [PATCH 14/17] drm/vc4: Remove unecessary dma_fence_ops Daniel Vetter
2018-04-30 17:50 ` Eric Anholt
2018-04-27 6:17 ` [PATCH 15/17] drm/vgem: " Daniel Vetter
2018-04-27 6:17 ` [PATCH 16/17] drm/virtio: " Daniel Vetter
2018-04-30 17:54 ` Eric Anholt
2018-04-27 6:17 ` [PATCH 17/17] dma-fence: Polish kernel-doc for dma-fence.c Daniel Vetter
2018-04-29 7:15 ` Christian König [this message]
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=0a579e7e-3432-a8b3-3bb5-f9a89cb212b2@gmail.com \
--to=ckoenig.leichtzumerken@gmail.com \
--cc=christian.koenig@amd.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.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