On Thu, Oct 20, 2016 at 8:47 AM, Chris Wilson <chris@xxxxxxxxxxxxxxxxxx> wrote: > I plan to usurp the short name of struct fence for a core kernel struct, > and so I need to rename the specialised fence/timeline for DMA > operations to make room. > > A consensus was reached in > https://lists.freedesktop.org/archives/dri-devel/2016-July/113083.html > that making clear this fence applies to DMA operations was a good thing. > Since then the patch has grown a bit as usage increases (and we wanted > to wait until after the sw_sync destage), so hopefully it remains a good > thing! > > I've pushed the patch to > > https://cgit.freedesktop.org/~ickle/linux-2.6/commit/?h=dma-fence&id=a4a27d87e4fccefb9f9d55f9c73ccab8f2ade3cc > > as I suspect it might be too large for the list. > > Highlights of the change: > > struct fence -> struct dma_fence (and all fence*() to dma_fence*()) > struct fence_array -> struct dma_fence_array > > 107 files changed, 1174 insertions(+), 1136 deletions(-) > > Mostly generated with the provided cocci spatch, but even with > --include-headers it seemed to miss some headers, and I never quite > worked out the substition commands for macros, so there is some grep and > replace. For merging I think the best would be to do a topic branch on top of drm-next, with 4.9-rc2, drm-misc and drm-intel all pulled in. Topic branch (and not drm-misc) so that we can rebase, and give 0day a few days to crunch through all the combinatorial Kconfigs ... -Daniel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
