On Fri, 2018-03-30 at 22:11 +0800, Daniel Stone wrote:
> Now that mtk_drm_fb is an empty wrapper around drm_framebuffer, we can
> just delete it.
>
Reviewed-by: CK Hu
> Signed-off-by: Daniel Stone
> Cc: CK Hu
> Cc: Philipp Zabel
> ---
> drivers/gpu/drm/mediatek/mtk_drm_fb.c | 40
>
On Fri, Mar 30, 2018 at 03:11:24PM +0100, Daniel Stone wrote:
> Now that mtk_drm_fb is an empty wrapper around drm_framebuffer, we can
> just delete it.
>
> Signed-off-by: Daniel Stone
> Cc: CK Hu
> Cc: Philipp Zabel
> ---
> drivers/gpu/drm/mediatek/mtk_drm_fb.c | 40
> ---
On Fri, Mar 30, 2018 at 03:11:24PM +0100, Daniel Stone wrote:
> Now that mtk_drm_fb is an empty wrapper around drm_framebuffer, we can
> just delete it.
>
> Signed-off-by: Daniel Stone
> Cc: CK Hu
> Cc: Philipp Zabel
Reviewed-by: Sean Paul
> ---
> drivers/gpu/drm/mediatek/mtk_drm_fb.c | 40
Hi CK, Philipp,
On 30 March 2018 at 15:11, Daniel Stone wrote:
> Now that mtk_drm_fb is an empty wrapper around drm_framebuffer, we can
> just delete it.
Did you get a chance to look at these three patches for Mediatek?
Cheers,
Daniel
___
dri-devel ma
Now that mtk_drm_fb is an empty wrapper around drm_framebuffer, we can
just delete it.
Signed-off-by: Daniel Stone
Cc: CK Hu
Cc: Philipp Zabel
---
drivers/gpu/drm/mediatek/mtk_drm_fb.c | 40 ---
1 file changed, 14 insertions(+), 26 deletions(-)
diff --git a/dri
