On Wed, Oct 26, 2016 at 07:45:14PM -0200, Gustavo Padovan wrote:
>
>%p should be kept for your internal debug only. Make sure to remove
>anything that exposes kernel address when sending patches.
>
>Gustavo
>
Noted, thanks!
-Brian
2016-10-26 Brian Starkey :
> Some parts of setting up the CRTC out-fence can be re-used for
> writeback out-fences. Factor this out into a separate function.
>
> Signed-off-by: Brian Starkey
> ---
> drivers/gpu/drm/drm_atomic.c | 64
> +++---
> 1 file chan
2016-10-26 Brian Starkey :
> Some parts of setting up the CRTC out-fence can be re-used for
> writeback out-fences. Factor this out into a separate function.
>
> Signed-off-by: Brian Starkey
> ---
> drivers/gpu/drm/drm_atomic.c | 64
> +++---
> 1 file chan
On Wed, Oct 26, 2016 at 09:55:06AM +0100, Brian Starkey wrote:
> Some parts of setting up the CRTC out-fence can be re-used for
> writeback out-fences. Factor this out into a separate function.
>
> Signed-off-by: Brian Starkey
Cc: Gustavo here pls, probably best if he reviews this one.
-Daniel
Hi Gustavo,
As Daniel rightly pointed out you would likely be interested in this
patch.
This is on-top of your v5 patch-set, with the bug-fixes I mentioned
before. I haven't dropped the fence_get(), as I figured you're
probably going to rebase your patches on top of the fence_get() in
sync_file_c
Some parts of setting up the CRTC out-fence can be re-used for
writeback out-fences. Factor this out into a separate function.
Signed-off-by: Brian Starkey
---
drivers/gpu/drm/drm_atomic.c | 64 +++---
1 file changed, 42 insertions(+), 22 deletions(-)
diff