Re: [PATCH v3 0/7] drm/atomic: Add accessor macros for all atomic state.

2017-02-12 Thread Laurent Pinchart
Hi Maarten, Do you plan to post a v4 ? I have two drivers that depends on this series for fence support, and I'd like to get that merged in v4.12. On Monday 16 Jan 2017 10:37:37 Maarten Lankhorst wrote: > Fourth iteration. Instead of trying to convert all drivers straight away, > implement all

Re: [Intel-gfx] [PATCH v3 0/7] drm/atomic: Add accessor macros for all atomic state.

2017-01-23 Thread Daniel Vetter
On Tue, Jan 17, 2017 at 02:45:32AM +0200, Laurent Pinchart wrote: > Hi Maarten, > > Thank you for the patches. > > On Monday 16 Jan 2017 10:37:37 Maarten Lankhorst wrote: > > Fourth iteration. Instead of trying to convert all drivers straight away, > > implement all macros that are required to

Re: [PATCH v3 0/7] drm/atomic: Add accessor macros for all atomic state.

2017-01-16 Thread Laurent Pinchart
Hi Maarten, One more thing. On Monday 16 Jan 2017 10:37:37 Maarten Lankhorst wrote: > Fourth iteration. Instead of trying to convert all drivers straight away, > implement all macros that are required to get state working. > > Old situation: > Use obj->state, which can refer to old or new

Re: [PATCH v3 0/7] drm/atomic: Add accessor macros for all atomic state.

2017-01-16 Thread Laurent Pinchart
Hi Maarten, Thank you for the patches. On Monday 16 Jan 2017 10:37:37 Maarten Lankhorst wrote: > Fourth iteration. Instead of trying to convert all drivers straight away, > implement all macros that are required to get state working. > > Old situation: > Use obj->state, which can refer to old

[PATCH v3 0/7] drm/atomic: Add accessor macros for all atomic state.

2017-01-16 Thread Maarten Lankhorst
Fourth iteration. Instead of trying to convert all drivers straight away, implement all macros that are required to get state working. Old situation: Use obj->state, which can refer to old or new state. Use drm_atomic_get_(existing_)obj_state, which can refer to new or old state. Use