Re: [PATCH 19/24] drm/armada: Move GEM BO to drm_framebuffer

2018-06-27 Thread Daniel Stone
Hi Russell, On Tue, 26 Jun 2018 at 15:49, Russell King - ARM Linux wrote: > On Thu, May 17, 2018 at 04:41:35PM +0100, Daniel Stone wrote: > > Thanks Russell. I did do a build test locally as well which had no > > complaints. I'll merge this through drm-misc. > > I've not seen this go in during

Re: [PATCH 19/24] drm/armada: Move GEM BO to drm_framebuffer

2018-06-27 Thread Russell King - ARM Linux
On Thu, May 17, 2018 at 04:41:35PM +0100, Daniel Stone wrote: > On 17 May 2018 at 16:26, Russell King - ARM Linux > wrote: > > On Thu, May 17, 2018 at 02:15:40PM +0100, Daniel Stone wrote: > >> On 30 March 2018 at 15:11, Daniel Stone wrote: > >> > Since drm_framebuffer can now store GEM objects

Re: [PATCH 19/24] drm/armada: Move GEM BO to drm_framebuffer

2018-05-18 Thread Russell King - ARM Linux
On Thu, May 17, 2018 at 02:15:40PM +0100, Daniel Stone wrote: > Hi Russell, > > On 30 March 2018 at 15:11, Daniel Stone wrote: > > Since drm_framebuffer can now store GEM objects directly, place them > > there rather than in our own subclass. As this makes the framebuffer

Re: [PATCH 19/24] drm/armada: Move GEM BO to drm_framebuffer

2018-05-17 Thread Daniel Stone
On 17 May 2018 at 16:26, Russell King - ARM Linux wrote: > On Thu, May 17, 2018 at 02:15:40PM +0100, Daniel Stone wrote: >> On 30 March 2018 at 15:11, Daniel Stone wrote: >> > Since drm_framebuffer can now store GEM objects directly, place them >> >

Re: [PATCH 19/24] drm/armada: Move GEM BO to drm_framebuffer

2018-05-17 Thread Thierry Reding
On Fri, Mar 30, 2018 at 03:11:33PM +0100, Daniel Stone wrote: > Since drm_framebuffer can now store GEM objects directly, place them > there rather than in our own subclass. As this makes the framebuffer > create_handle and destroy functions the same as the GEM framebuffer > helper, we can reuse

Re: [PATCH 19/24] drm/armada: Move GEM BO to drm_framebuffer

2018-05-17 Thread Daniel Stone
Hi Russell, On 30 March 2018 at 15:11, Daniel Stone wrote: > Since drm_framebuffer can now store GEM objects directly, place them > there rather than in our own subclass. As this makes the framebuffer > create_handle and destroy functions the same as the GEM framebuffer >

[PATCH 19/24] drm/armada: Move GEM BO to drm_framebuffer

2018-03-30 Thread Daniel Stone
Since drm_framebuffer can now store GEM objects directly, place them there rather than in our own subclass. As this makes the framebuffer create_handle and destroy functions the same as the GEM framebuffer helper, we can reuse those. Signed-off-by: Daniel Stone Cc: Russell