On Wed, Jul 13, 2016 at 11:54:50PM +0900, Inki Dae wrote: > Hi, > > 2016-07-13 23:10 GMT+09:00 Chris Wilson <chris@xxxxxxxxxxxxxxxxxx>: > > 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. > > > > As an indication of the scale of the flag day: > > > > 91 files changed, 904 insertions(+), 880 deletions(-) > > Seems files changed and below patch codes are not inconsistent. i.e., > I cannot see modified codes for Android sync driver. The cut'n'paste doesn't include the renames which the patch below does (i..e. it should be a more accurate representation of lines changed by ignoring the lines moved). > And Android sync driver - explicit fence - can use a fence object > regardless of DMA buffer. So it looks reasonable to use 'fence' as-is. > Was there any changes for Android sync driver to be dependent on DMA buffer? This was based on Gustova Padovan's destaged sync tree, so all the Android changes should be inside drivers/dma-buf/*sync* I was using grep to find all users of struct fence and callers of fence_*() so I don't think I missed any drivers/staging/ - and obviously this will have to repeated closer to the flag day. -Chris -- Chris Wilson, Intel Open Source Technology Centre _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
