drm/gma500: Fix Medfield for drm_framebuffer move
authorDaniel Stone <daniels@collabora.com>
Mon, 21 May 2018 14:24:49 +0000 (15:24 +0100)
committerDaniel Stone <daniels@collabora.com>
Tue, 22 May 2018 09:26:38 +0000 (10:26 +0100)
commitc7cbed560ce24a87eccf219bc4c78a19961a6074
tree363c7ada14f8a4cd600354f04226122aa7985fb7
parent2ecceeb53b19455ffa50b31fd3c20fe2974508a6
drm/gma500: Fix Medfield for drm_framebuffer move

Commit bc61c97502e2 ("drm/gma500: Move GEM BO to drm_framebuffer") moved
the gtt_range structure, from being in psb_framebuffer and embedding the
GEM object, to being placed in the drm_framebuffer with the gtt_range
being derived from the GEM object.

The conversion missed out the Medfield subdriver, which was not being
built in the default drm-misc config. Do the trivial fixup here.

Signed-off-by: Daniel Stone <daniels@collabora.com>
Reported-by: kbuild test robot <lkp@intel.com>
Reviewed-by: Thierry Reding <treding@nvidia.com>
Fixes: bc61c97502e2 ("drm/gma500: Move GEM BO to drm_framebuffer")
Cc: Patrik Jakobsson <patrik.r.jakobsson@gmail.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20180521142449.20800-1-daniels@collabora.com
drivers/gpu/drm/gma500/mdfld_intel_display.c