CHROMIUM: drm/exynos: fb: Don't return errors when unmapping fb gem objects
authorDaniel Kurtz <djkurtz@chromium.org>
Thu, 3 Jan 2013 01:51:56 +0000 (09:51 +0800)
committerChromeBot <chrome-bot@google.com>
Sat, 5 Jan 2013 09:19:21 +0000 (01:19 -0800)
commitedc8f2515145510c0247494bddd8b58053b95681
tree12c86d24b29e73888831e1cee3253548fb2e041b
parentb1cbd07882e4d1e160c64153ccd42b4e09394e7d
CHROMIUM: drm/exynos: fb: Don't return errors when unmapping fb gem objects

Silently accept and ignore a NULL buffer or a buffer which has not yet
been mapped (i.e., its dma_addr is unset).

These aren't really errors (and I don't see how they are even possible).
Simplifying this lets the unmap function just return void.

Signed-off-by: Daniel Kurtz <djkurtz@chromium.org>
BUG=chromium-os:37097
TEST=builds clean; sanity check on device

Change-Id: Ib1fa50152b0444fbafc05ac8b712d69ffda962c5
Reviewed-on: https://gerrit.chromium.org/gerrit/40446
Commit-Queue: Daniel Kurtz <djkurtz@chromium.org>
Reviewed-by: Daniel Kurtz <djkurtz@chromium.org>
Tested-by: Daniel Kurtz <djkurtz@chromium.org>
drivers/gpu/drm/exynos/exynos_drm_fb.c